diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-04-20 11:04:00 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-04-20 11:57:54 -0700 |
commit | be913e7c4034bd7a5cbfc3d53188344dc588d45c (patch) | |
tree | 8bb44000d647cb1204da798e25d9c1be71db4a15 /drivers/acpi/tables.c | |
parent | 4b4bd8c50f4836ba7d3fcfd6c90f96d2605779fe (diff) | |
download | linux-stable-be913e7c4034bd7a5cbfc3d53188344dc588d45c.tar.gz linux-stable-be913e7c4034bd7a5cbfc3d53188344dc588d45c.tar.bz2 linux-stable-be913e7c4034bd7a5cbfc3d53188344dc588d45c.zip |
gcc-15: get rid of misc extra NUL character padding
This removes two cases of explicit NUL padding that now causes warnings
because of '-Wunterminated-string-initialization' being part of -Wextra
in gcc-15.
Gcc is being silly in this case when it says that it truncates a NUL
terminator, because in these cases there were _multiple_ NUL characters.
But we can get rid of the warning by just simplifying the two
initializers that trigger the warning for me, so this does exactly that.
I'm not sure why the power supply code did that odd
.attr_name = #_name "\0",
pattern: it was introduced in commit 2cabeaf15129 ("power: supply: core:
Cleanup power supply sysfs attribute list"), but that 'attr_name[]'
field is an explicitly sized character array in a statically initialized
variable, and a string initializer always has a terminating NUL _and_
statically initialized character arrays are zero-padded anyway, so it
really seems to be rather extraneous belt-and-suspenders.
The zero_uuid[16] initialization in drivers/md/bcache/super.c makes
perfect sense, but it isn't necessary for the same reasons, and not
worth the new gcc warning noise.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/acpi/tables.c')
0 files changed, 0 insertions, 0 deletions