On Sep 22, 2014, at 1:33 PM, Borislav Petkov <bp@xxxxxxxxx> wrote: > Btw, out of curiosity, what is your use case for staring at those W=2 > warnings? I know no one cares about out-of-tree drivers, but I have a hack that allows building out-of-tree drivers without getting warnings from the kernel includes. We do an automated compile of every patch with W=12 and expect clean compiles. It would be nice to compile drivers in-tree and have a similar expectation. I guess a similar hack could be developed, but since we are contributing upstream, I would rather uncover any potential issues that may exist, even if they aren't in the driver. The hack would tend to cover up such issues. This is definitely NOT about covering up things that could be problems! > In thinking about it, what we could also do is simply move the noisiest > ones to W=3 or so, or even add another W= level. It'll be interesting to > hear your use case though. AFAICT, this is the first time I hear of a > more, let's say, serious use case of W= since we added the W= things a > couple of years ago. :-) Well, I have W=1 in my environment, so I don't even have to ask for it, I just get it. W=12 is just insane, or I would use that all the time. I think it would be nice for new code, or at least new drivers, to compile clean with W=12, but that isn't possible when the kernel includes throw so many warnings. Nested-externs, for example, can catch people gratuitously providing a function prototype that could become a hazard, but some use of that may be justified. The macros provide a way to specifically allow certain instances while generally discouraging it. Of course if you never use W=2 you may never catch those gratuitous declarations. > Thanks. Hopefully the discussion is somewhat useful. -- Mark Rustad, Networking Division, Intel Corporation
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
