From: Sam Ravnborg <sam@ravnborg.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: urs.thuermann@volkswagen.de, neilb@suse.de, greg@kroah.com,
bfields@fieldses.org, linux-mtd@lists.infradead.org,
dbrownell@users.sourceforge.net, x86 maintainers <x86@kernel.org>,
tiwai@suse.de, netfilter-devel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@infradead.org,
linux-raid@vger.kernel.org, netfilter@vger.kernel.org,
linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
oliver.hartkopp@volkswagen.de,
spi-devel-general@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [GIT PULL -tip] fix 33 make headers_check warnings
Date: Sun, 18 Jan 2009 11:10:29 +0100 [thread overview]
Message-ID: <20090118101029.GA31461@uranus.ravnborg.org> (raw)
In-Reply-To: <20090118091300.GA24849@elte.hu>
On Sun, Jan 18, 2009 at 10:13:00AM +0100, Ingo Molnar wrote:
>
> * Sam Ravnborg <sam@ravnborg.org> wrote:
>
> > On Sun, Jan 18, 2009 at 08:37:41AM +1100, David Woodhouse wrote:
> > > On Sun, 2009-01-18 at 01:47 +0530, Jaswinder Singh Rajput wrote:
> > > > --- a/include/linux/dvb/audio.h
> > > > +++ b/include/linux/dvb/audio.h
> > > > @@ -24,9 +24,8 @@
> > > > #ifndef _DVBAUDIO_H_
> > > > #define _DVBAUDIO_H_
> > > >
> > > > -#ifdef __KERNEL__
> > > > #include <linux/types.h>
> > > > -#else
> > > > +#ifndef __KERNEL__
> > > > #include <stdint.h>
> > > > #endif
> > > >
> > >
> > > That patch looks wrong, and unnecessary. It was fine before.
> > Nope - include/linux/dvb/audio.h failed to include linux/types.h
> > despite the fact that is uses __u32 etc.
> >
> > But why the _kernel_ should include a userspace header is
> > much more questionable.
>
> ok, i dropped this one for the time being.
>
> Sam, Andrew, et al, i've got the commit lineup below, to fix the ~200 new
> CONFIG_HEADERS_CHECK=y warnings we have in current -git, on x86
> allyesconfig.
>
> Note that i have restructured the tree and the commits so that this effort
> can be tracked more easily: each commit has a "headers_check fix" subject
> line prefix. So you can go back later and revisit these things - for
> example whether a header really needs to be exported to user-space, via:
>
> git log --grep='headers_check fix:' --pretty=format:"%h: %s"
>
> to get an overview and a historic track record. We can follow this
> notation in the future too.
>
> So if there are no objections, i'll send this to Linus tomorrow-ish and
> we'll have the worst of the fallout behind us and can embark on a much
> more fluid (and per maintainer) headers_check related workflow.
Thanks for taking care of this Ingo and please push towards Linus.
And thanks to all the contributors too - it was great to see this dealt
with soo quickly!
Sam
next prev parent reply other threads:[~2009-01-18 10:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 20:17 [GIT PULL -tip] fix 33 make headers_check warnings Jaswinder Singh Rajput
2009-01-17 21:37 ` David Woodhouse
2009-01-17 22:04 ` Jan Engelhardt
2009-01-17 22:19 ` Sam Ravnborg
2009-01-17 22:23 ` David Woodhouse
2009-01-18 2:46 ` Jaswinder Singh Rajput
2009-01-17 22:26 ` H. Peter Anvin
2009-01-21 0:38 ` Jaswinder Singh Rajput
2009-01-23 15:59 ` Jaswinder Singh Rajput
2009-01-23 16:04 ` Jaswinder Singh Rajput
2009-01-23 16:11 ` Jan Engelhardt
2009-01-23 16:21 ` Sam Ravnborg
2009-01-23 16:31 ` Jaswinder Singh Rajput
2009-01-23 17:09 ` Sam Ravnborg
2009-01-23 17:28 ` Jaswinder Singh Rajput
2009-01-23 21:33 ` H. Peter Anvin
2009-01-23 21:54 ` Jan Engelhardt
2009-01-23 22:01 ` H. Peter Anvin
2009-01-18 3:05 ` Jaswinder Singh Rajput
2009-01-18 3:33 ` Kyle McMartin
2009-01-18 3:38 ` Jaswinder Singh Rajput
2009-01-18 4:18 ` Kyle McMartin
2009-01-23 15:56 ` Jaswinder Singh Rajput
2009-01-18 9:13 ` Ingo Molnar
2009-01-18 10:10 ` Sam Ravnborg [this message]
2009-01-19 0:24 ` Stephen Rothwell
2009-01-19 2:53 ` Jaswinder Singh Rajput
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=20090118101029.GA31461@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=dbrownell@users.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tiwai@suse.de \
--cc=urs.thuermann@volkswagen.de \
--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