From: Andrew Morton <akpm@linux-foundation.org>
To: James Morris <jmorris@namei.org>
Cc: adobriyan@gmail.com, linux-kernel@vger.kernel.org, dhowells@redhat.com
Subject: Re: [PATCH] cred: #include init.h in cred.h
Date: Mon, 11 May 2009 15:48:57 -0700 [thread overview]
Message-ID: <20090511154857.eacb2788.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LRH.2.00.0905120831560.3090@tundra.namei.org>
On Tue, 12 May 2009 08:32:31 +1000 (EST)
James Morris <jmorris@namei.org> wrote:
> On Mon, 11 May 2009, Andrew Morton wrote:
>
> > On Sat, 9 May 2009 07:36:52 +0400
> > Alexey Dobriyan <adobriyan@gmail.com> wrote:
> >
> > > linux/cred.h can't be included as first header (alphabetical order)
> > > because it uses __init which is enough to break compilation on some
> > > archs.
> > >
> >
> > hm, OK, not a lot of detail there though.
> >
> > >
> > > --- a/include/linux/cred.h
> > > +++ b/include/linux/cred.h
> > > @@ -13,6 +13,7 @@
> > > #define _LINUX_CRED_H
> > >
> > > #include <linux/capability.h>
> > > +#include <linux/init.h>
> > > #include <linux/key.h>
> > > #include <asm/atomic.h>
> >
> > I assume that this is needed in 2.6.30?
> >
>
> I can see it's in -mm, so might as well go to Linus via there.
No prob.
> Acked-by: James Morris <jmorris@namei.org>
Thanks.
This is not the sort of patch which I'd send upstream immediately.
cred.h is included by sched.h and sched.h doesn't include init.h.
That's enough uncertainty to require a few days compile-testing..
prev parent reply other threads:[~2009-05-11 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 3:36 [PATCH] cred: #include init.h in cred.h Alexey Dobriyan
2009-05-11 20:20 ` Andrew Morton
2009-05-11 21:16 ` Alexey Dobriyan
2009-05-11 22:32 ` James Morris
2009-05-11 22:48 ` Andrew Morton [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=20090511154857.eacb2788.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.