Re: [resend][PATCH] avoid signed vs unsigned comparison in efi_range_is_wc()

From: Arnd Bergmann
Date: Thu Jun 16 2005 - 16:53:23 EST

On Dunnersdag 16 Juni 2005 23:02, Jesper Juhl wrote:
> On Thu, 16 Jun 2005, Andrew Morton wrote:
> > There are surely many warnings in the tree, hence I'm not really interested
> > in patches which only fix `gcc -W' warnings.
> >
> Ok, in that case I won't bother you directly with such patches any more
> but instead let them trickle into maintainers trees when they will take
> them.
> And yes, I know it's very trivial stuff and it doesn't make much of a
> difference to the "big picture", but my attitude towards that is that no
> issue is too small to be addressed, and since I'm not able to adress many
> of the larger issues I try to address the smaller ones that I'm able to
> handle, and when I run out of those I start nitpicking with the really
> trivial stuff (like gcc -W warnings) - all with the purpose of helping our
> kernel be the very best it can, even if my contribution might be very
> minor in some cases.

I have a patch that optionally enables some of the interesting warnings
that gcc supports (e.g. -Wmissing-format-attribute -Wmissing-declarations
-Wundef -Wwrite-strings).

It has four different levels:

- quiet (current warnings minus -Wdeprecated-declarations)
- normal (some interesting ones added that are not too noisy)
- more (all interesting ones, including some noisier ones like
- overkill (-W and some more that only make sense for statistic

I have the base patch and some more patches that fix the most annoying
warnings. I find them more useful than the signed vs unsigned comparison
fixes you are doing right now, but don't have the time to split my
patches up into obvious chunks.

Jesper, are you interested in my stuff and willing to continue that work?
I'd suggest to fix the warnings at 'normal' level first and then
integrate the patch for configurable warning levels into -mm.

Arnd <><
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at