From: Arnd Bergmann <arnd@arndb.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?]
Date: Fri, 23 May 2008 00:52:45 +0200 [thread overview]
Message-ID: <200805230052.46976.arnd@arndb.de> (raw)
In-Reply-To: <20080522013035.GV28946@ZenIV.linux.org.uk>
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 <><
next prev parent reply other threads:[~2008-05-22 22:53 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 21:20 Moving sound/* to drivers/ ? Takashi Iwai
2008-05-21 21:20 ` Takashi Iwai
2008-05-21 21:44 ` Linus Torvalds
2008-05-21 21:44 ` Linus Torvalds
2008-05-21 21:54 ` Sam Ravnborg
2008-05-21 21:54 ` Sam Ravnborg
2008-05-21 21:58 ` Rene Herman
2008-05-21 21:58 ` [alsa-devel] " Rene Herman
2008-05-21 22:08 ` Rene Herman
2008-05-21 23:21 ` Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?] Paul Mackerras
2008-05-21 23:51 ` Linus Torvalds
2008-05-22 0:56 ` Al Viro
2008-05-22 1:20 ` Linus Torvalds
2008-05-22 1:23 ` Moving include/asm-* David Miller
2008-05-22 8:09 ` Andreas Schwab
2008-05-22 16:12 ` David Miller
2008-05-22 16:32 ` Andreas Schwab
2008-05-22 17:43 ` David Miller
2008-05-22 1:23 ` Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?] Harvey Harrison
2008-05-22 1:25 ` Moving include/asm-* David Miller
2008-05-22 1:29 ` Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?] Linus Torvalds
2008-05-22 1:36 ` Al Viro
2008-05-22 4:20 ` Jeff Dike
2008-05-22 5:26 ` Al Viro
2008-05-22 16:27 ` Jeff Dike
2008-05-22 17:18 ` Sam Ravnborg
2008-05-22 1:30 ` Al Viro
2008-05-22 22:52 ` Arnd Bergmann [this message]
2008-05-21 22:05 ` Moving sound/* to drivers/ ? Timur Tabi
2008-05-21 22:05 ` [alsa-devel] " Timur Tabi
2008-05-21 22:23 ` Adrian Bunk
2008-05-22 8:22 ` Takashi Iwai
2008-05-22 8:22 ` Takashi Iwai
2008-05-21 23:37 ` Jeff Garzik
2008-05-21 23:53 ` Rene Herman
2008-05-21 23:53 ` Rene Herman
2008-05-22 6:26 ` Jaroslav Kysela
2008-05-22 6:26 ` Jaroslav Kysela
2008-05-22 7:12 ` Sam Ravnborg
2008-05-22 7:12 ` Sam Ravnborg
2008-05-22 7:20 ` Jaroslav Kysela
2008-05-22 7:20 ` Jaroslav Kysela
2008-05-22 8:11 ` Rene Herman
2008-05-22 8:11 ` Rene Herman
2008-05-22 8:27 ` Takashi Iwai
2008-05-22 8:27 ` Takashi Iwai
2008-05-22 8:55 ` Jan Engelhardt
2008-05-22 15:04 ` Linus Torvalds
2008-05-22 15:04 ` Linus Torvalds
2008-05-22 15:50 ` Jan Engelhardt
2008-05-22 16:40 ` Rene Herman
2008-05-22 16:40 ` Rene Herman
2008-05-22 9:57 ` Rene Herman
2008-05-22 9:57 ` Rene Herman
2008-05-22 14:22 ` Adrian Bunk
2008-05-22 14:22 ` Adrian Bunk
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=200805230052.46976.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.