https://bugzilla.kernel.org/show_bug.cgi?id=207959 --- Comment #7 from Luc Van Oostenryck (luc.vanoostenryck@xxxxxxxxx) --- (In reply to Linus Torvalds from comment #5) > That said, I'm not sure the kernel cares. If sparse makes '{ 0 }' be > equivalent to '{ }' and doesn't warn for it, it's not like it's a huge deal. > > The problem with using 0 instead of NULL (or vice versa, which is a crime, > and which is why NULL should never have been defined to plain 0) comes when > it is actually confusing. OK. I also detest this 'you can use 0 for pointers' but I think that '{ 0 }' should just be understood as the standard idiom for '{ }' and that the current situation where '{ 0 }' gives warnings while '{ }' doesn't s confusing and annoying. So, I'll change Sparse's default to -Wno-universal-initializer. > So I'd prefer the "0 for NULL" warning, even if this may not be the most > important case for it. Do you think it's worth to add -Wuniversal-initializer for the kernel so that these warnings are still present for '{ 0 }'? -- Luc -- You are receiving this mail because: You are watching the assignee of the bug.
