linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Juhl <juhl-lkml@dif.dk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jesper Juhl <juhl-lkml@dif.dk>, Andrew Morton <akpm@osdl.org>,
	davidm@hpl.hp.com, eranian@hpl.hp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [resend][PATCH] avoid signed vs unsigned comparison in efi_range_is_wc()
Date: Fri, 17 Jun 2005 00:24:10 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0506170014440.2477@dragon.hyggekrogen.localhost> (raw)
In-Reply-To: <200506162348.38423.arnd@arndb.de>

On Thu, 16 Jun 2005, Arnd Bergmann wrote:

> 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 
>   -Wmissing-declarations)
> - overkill (-W and some more that only make sense for statistic
>   analysis)
> 
> 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

Certainly.


> and willing to continue that work?

To the best of my abilities, yes. I'd like to take a look at those 
patches. 
If nothing else it sounds like a good way for me to cut my current 
(extra warning enabled) build logs down to size and focus on the more 
relevant of the issues. And perhaps, if I can find the time for it, I can 
split the other patches you have into some sane chunks and start 
submitting them to the relevant maintainers.


> I'd suggest to fix the warnings at 'normal' level first and then
> integrate the patch for configurable warning levels into -mm.
> 
Sounds like a resonable plan to me.  Send your stuff along and I'll put 
some time into it when and where I can find it :-)


--
Jesper 



  reply	other threads:[~2005-06-16 22:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 20:21 [resend][PATCH] avoid signed vs unsigned comparison in efi_range_is_wc() Jesper Juhl
2005-06-16 20:41 ` Andrew Morton
2005-06-16 21:02   ` Jesper Juhl
2005-06-16 21:48     ` Arnd Bergmann
2005-06-16 22:24       ` Jesper Juhl [this message]
2005-06-16 20:45 ` Richard B. Johnson
2005-06-16 21:07   ` Jesper Juhl
2005-06-16 21:32     ` Arnd Bergmann
2005-06-16 21:01 ` David Mosberger
2005-06-20 17:00   ` Jesse Barnes
2005-06-17  0:25 Arnd Bergmann <arnd@arndb.de>
2005-06-17 17:04 ` Jesper Juhl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.62.0506170014440.2477@dragon.hyggekrogen.localhost \
    --to=juhl-lkml@dif.dk \
    --cc=akpm@osdl.org \
    --cc=arnd@arndb.de \
    --cc=davidm@hpl.hp.com \
    --cc=eranian@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).