From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Takashi Iwai <tiwai@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Moving include/asm-* [was: Re: Moving sound/* to drivers/ ?]
Date: Wed, 21 May 2008 16:51:57 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805211635040.3081@woody.linux-foundation.org> (raw)
In-Reply-To: <18484.44691.477859.334222@cargo.ozlabs.ibm.com>
On Thu, 22 May 2008, Paul Mackerras wrote:
>
> Linus Torvalds writes:
>
> > Me personally, I've been more irritated by include/asm-xyz vs arch/xyz. It
> > would be so nice if all the arch-specific changes woudl always show up
> > under arch/ (both from a statistics standpoint, and just because then a
> > diffstat really shows arch-specific stuff really obviously, and sorts all
> > the arch-specific stuff together).
>
> We could git mv include/asm-xyz arch/xyz/asm and then arrange to pass
> -Iarch/$(ARCH) to gcc.
That would work, but there's a few alternatives that I think would work
even better.
The downside with what you suggest is that I'd like the arch-specific
include files to be clearly separated (ie I think the naming should be
"something/include/something", which makes things clearer.
Also, I hate how doing '-Iarch/$(ARCH)' would basically make any random
arch/xyz/ subdirectory be a potential location for a header file. I'd hate
for the include-path to contain subdirectories that simply aren't meant
for that (ie #include <kernel/tls.h> would now quite by mistake find the
*private* header file in arch/x86/kernel/tls.h that was never meant to be
generally visible!)
So the trivial alternative is to just do
git mv include/asm-xyz arch/xyz/include
and keep the symlink that we already set up (just make it point to
arch/xyz/include instead of include/asm-xyz). That is conceptually the
smallest change.
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.
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.
I dunno. It's not a huge deal, but it really would be nice to have all the
arch/xyz code together for diffstat's etc.
Linus
next prev parent reply other threads:[~2008-05-21 23:52 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 [this message]
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
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=alpine.LFD.1.10.0805211635040.3081@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®