On 2/13/07, Sergei Organov <[email protected]> wrote:
With almost any warning out there one makes more or less efforts to suppress the warning where it gives false positives, isn't it?
Yes, as long it's the _compiler_ that's doing the effort. You shouldn't need to annotate the source just to make the compiler shut up. Once the compiler starts issuing enough false positives, it's time to turn off that warning completely. Therefore, the only sane strategy for a warning is to aim for zero false positives. Pekka - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: somebody dropped a (warning) bomb
- From: Sergei Organov <[email protected]>
- Re: somebody dropped a (warning) bomb
- References:
- somebody dropped a (warning) bomb
- From: Jeff Garzik <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Linus Torvalds <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Linus Torvalds <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Sergei Organov <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Linus Torvalds <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Sergei Organov <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Linus Torvalds <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Sergei Organov <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: "Pekka Enberg" <[email protected]>
- Re: somebody dropped a (warning) bomb
- From: Sergei Organov <[email protected]>
- somebody dropped a (warning) bomb
- Prev by Date: Re: [PATCH v2] kernel-doc: include struct short description in title output
- Next by Date: RE: Intel 82559 NIC corrupted EEPROM
- Previous by thread: Re: somebody dropped a (warning) bomb
- Next by thread: Re: somebody dropped a (warning) bomb
- Index(es):