From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Mackerras <paulus@samba.org>, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?]
Date: Thu, 22 May 2008 01:56:57 +0100 [thread overview]
Message-ID: <20080522005657.GU28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.1.10.0805211635040.3081@woody.linux-foundation.org>
On Wed, May 21, 2008 at 04:51:57PM -0700, Linus Torvalds wrote:
> So the trivial alternative is to just do
>
> git mv include/asm-xyz arch/xyz/include
Careful - arch/um/include/ exists, so that'll get interesting.
> But the alternative I'd actually *prefer* would avoid the symlink, and
> would be roughly:
>
> for i in $(arch-list)
> do
> mkdir arch/$i/include
> git mv include/asm-$i arch/$i/asm
>
> done
> git mv include/asm-generic include/asm
>
> and then remove the symlink to asm entirely, and instead add a
> -Iarch/xyz/include, and put that as the *first* entry in the include path.
Eh? git mv include/asm-$i arch/$i/include/asm, then?
> This would mean that:
>
> - no symlink games
>
> - if some architecture just uses the generic header file, it doesn't need
> to do anything: it just wouldn't implement that header file at all, and
> the next entry in the search-path would just find the generic
> include/asm entry.
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_...
next prev parent reply other threads:[~2008-05-22 0:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 21:20 Moving sound/* to drivers/ ? Takashi Iwai
2008-05-21 21:44 ` Linus Torvalds
2008-05-21 21:54 ` Sam Ravnborg
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 [this message]
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
2008-05-21 22:05 ` [alsa-devel] Moving sound/* to drivers/ ? Timur Tabi
2008-05-21 22:23 ` Adrian Bunk
2008-05-22 8:22 ` Takashi Iwai
2008-05-21 23:37 ` Jeff Garzik
2008-05-21 23:53 ` Rene Herman
2008-05-22 6:26 ` Jaroslav Kysela
2008-05-22 7:12 ` Sam Ravnborg
2008-05-22 7:20 ` Jaroslav Kysela
2008-05-22 8:11 ` Rene Herman
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:50 ` Jan Engelhardt
2008-05-22 16:40 ` Rene Herman
2008-05-22 9:57 ` Rene Herman
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=20080522005657.GU28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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