Lines Matching refs:warnings
61 false positive warnings from kmemcheck. An example of this is a 16-bit
90 information from the kmemcheck warnings, which is extremely valuable in
115 can prevent floods of warnings and increase the chances of the machine
146 warnings might overflow the kernel log itself, and the earlier reports
176 This option silences warnings that would be generated for bit-field
220 positive warnings to appear. Therefore, try not to use this. If you find that
221 it doesn't work properly (e.g. you see an unreasonable amount of warnings), I
655 /* No warnings will ever trigger on accessing any part of x */
685 /* No warnings will trigger on accessing the bitfield of x */
697 is not very wise to blindly post kmemcheck warnings to mailing lists and
751 object in question as being initialized so that no warnings will ever be