From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
Jaswinder Singh Rajput <jaswinder@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PULL -tip] fixed few make headers_check warnings
Date: Thu, 15 Jan 2009 15:49:34 +0100 [thread overview]
Message-ID: <20090115144934.GA872@elte.hu> (raw)
In-Reply-To: <20090115143717.GA11991@uranus.ravnborg.org>
* Sam Ravnborg <sam@ravnborg.org> wrote:
> On Thu, Jan 15, 2009 at 12:11:34PM +0100, Ingo Molnar wrote:
> >
> > * Sam Ravnborg <sam@ravnborg.org> wrote:
> >
> > > So when I see "capability.h: extern's make no sense in userspace" the
> > > perfect approach would be that the whole file was checked.
> > >
> > > This is a much bigger task that just removing the warning.
> >
> > The problem is, you just littered the kernel with a ton of warnings and
> > declared that fixing them is a 'much bigger task'.
> >
> > It's not good to start projects like this, because they simply never
> > finish. It's _much_ better to first reach a zero baseline via minimal
> > fixes, then enforce 'look at the whole thing' for all _NEW_ files and
> > changes.
> >
> > That's how we are using checkpatch in the -tip topics, and it's working
> > very nicely.
> >
> > Could we please start it like that?
>
> I would have done such have I had more time to do this stuff. Real life
> just hit me after vacation finished and deadline approaching.
>
> I can disable the warnings around -rc7 if we think they are too noisy
> when we release the next kernel.
they are perfectly fine i think, lets just not do the full approach now
and reach a zero baseline first. Then perfectionism can start again, at a
much more manageable flux.
Ingo
prev parent reply other threads:[~2009-01-15 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 8:40 [PULL -tip] fixed few make headers_check warnings Jaswinder Singh Rajput
2009-01-13 12:49 ` Ingo Molnar
2009-01-13 21:03 ` David Miller
2009-01-14 15:40 ` Sam Ravnborg
2009-01-14 15:58 ` Oliver Hartkopp
2009-01-15 10:54 ` Ingo Molnar
2009-01-14 8:56 ` Geert Uytterhoeven
2009-01-14 9:29 ` Jaswinder Singh Rajput
2009-01-14 15:38 ` Sam Ravnborg
2009-01-14 15:59 ` Jaswinder Singh Rajput
2009-01-14 16:36 ` Geert Uytterhoeven
2009-01-14 16:58 ` Jaswinder Singh Rajput
2009-01-14 20:15 ` Sam Ravnborg
2009-01-15 11:11 ` Ingo Molnar
2009-01-15 14:37 ` Sam Ravnborg
2009-01-15 14:47 ` Jaswinder Singh Rajput
2009-01-15 14:50 ` Ingo Molnar
2009-01-15 14:51 ` Ingo Molnar
2009-01-15 15:16 ` Jaswinder Singh Rajput
2009-01-15 15:33 ` Ingo Molnar
2009-01-15 14:49 ` Ingo Molnar [this message]
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=20090115144934.GA872@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jaswinder@infradead.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=x86@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).