[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200805230052.46976.arnd@arndb.de>
Date: Fri, 23 May 2008 00:52:45 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Paul Mackerras <paulus@...ba.org>,
Takashi Iwai <tiwai@...e.de>, linux-kernel@...r.kernel.org,
David Miller <davem@...emloft.net>
Subject: Re: Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?]
On Thursday 22 May 2008, Al Viro wrote:
> On Wed, May 21, 2008 at 06:20:27PM -0700, Linus Torvalds wrote:
> > On Thu, 22 May 2008, Al Viro wrote:
> >
> > > Nice, but... how do you pull what's currently asm-generic/foo.h from what's
> > > currently asm-bar/foo.h? #include_next is _ugly_...
> >
> > I was actually going to suggest #include_next, yes. But if people hate it,
> > we can certainly just keep the current <asm-generic/xyz.h> approach.
>
> Another alternative is to replace asm-generic/ with generic/asm and have
> -I include -I arch/$ARCH/include -I include/generic. Then we'd have
Neither #include_next nor the generic/asm approach seems to have a
straightforward way of handling exported user space headers.
The current include/asm-generic way of doing this isn't nice either,
but at least it's a known evil.
Since the question of asm-generic is almost entirely independent of
where the regular arch headers are, I'd vote for leaving asm-generic
alone for now and only doing the obvious move of all other headers to
arch/*/include/asm as a significant step in the right direction.
Nobody seemed to object that part so far, and the only significant
changes it needs are in sparc64, m68knommu and um as well as a few
scripts changes.
Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists