From: Sam Ravnborg <sam@ravnborg.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Support arch/$ARCH/include in kbuild
Date: Mon, 23 Jun 2008 00:05:09 +0200 [thread overview]
Message-ID: <20080622220508.GA8957@uranus.ravnborg.org> (raw)
In-Reply-To: <20080621220703.GA12279@uranus.ravnborg.org>
On Sun, Jun 22, 2008 at 12:07:03AM +0200, Sam Ravnborg wrote:
> Linus hinted that he liked to have all arch specific
> header files moved from include/asm-$ARCH to
> arch/$ARCH/include/asm.
>
> The following two patches implement the basic support
> for this.
>
> I have used sparc for my testing and to some degree
> I also used i386.
>
> For sparc I just had to do a simple:
>
> mkdir -p arch/sparc/include/asm
> mv include/asm-sparc/* arch/sparc/include/asm
>
> to build sparc with the new directory layout.
>
> For i386 I had to do a few trivial path fixes in
> arch/x86/Makefile and to fix the include of unistd_32.h
> in one place to fix the build.
>
> I expect a few additional bits to show up when people
> start to move their header files but this should
> be a good starting point.
>
>
> To support arch/$ARCH/include/ was done in two steps.
>
> First was to teach make headers_* about the new layout.
> And second step was to get the build fixed with the new
> layout.
>
> Patches are on top of kbuild-next.git and follows.
I redid this and ended up with 5 small patches.
Sam Ravnborg (5):
kbuild: prepare headers_* for arch/$ARCH/include
kbuild: include/asm may be a file - fix mrproper for this
kbuild: support arch/$ARCH/include for tags, cscope
kbuild: asm symlink support for arch/$ARCH/include
kbuild: add arch/$ARCH/include to search path
This patchset is tested a more than
the previous one and is now also pushed out
to kbuild-next.git so it will apprear in -next shortly.
There were a few bugs around the symlink handling
and make tags is now also functional.
So I consider this ready for merging.
Any comments are welcome!
Patches will follow as reply to this one, but they
are only sent to kbuild and lkml.
Sam
next prev parent reply other threads:[~2008-06-22 22:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 22:07 Support arch/$ARCH/include in kbuild Sam Ravnborg
2008-06-21 22:08 ` [PATCH] kbuild: prepare headers_* for arch/$ARCH/include Sam Ravnborg
2008-06-21 22:08 ` [PATCH] kbuild: support arch/$ARCH/include/ Sam Ravnborg
2008-06-21 22:11 ` Support arch/$ARCH/include in kbuild Sam Ravnborg
2008-06-22 22:05 ` Sam Ravnborg [this message]
2008-06-22 22:08 ` [PATCH 1/5] kbuild: prepare headers_* for arch/$ARCH/include Sam Ravnborg
2008-06-24 14:31 ` Arnd Bergmann
2008-06-22 22:08 ` [PATCH 2/5] kbuild: include/asm may be a file - fix mrproper for this Sam Ravnborg
2008-06-22 22:08 ` [PATCH 3/5] kbuild: support arch/$ARCH/include for tags, cscope Sam Ravnborg
2008-06-22 22:08 ` [PATCH 4/5] kbuild: asm symlink support for arch/$ARCH/include Sam Ravnborg
2008-06-22 22:08 ` [PATCH 5/5] kbuild: add arch/$ARCH/include to search path Sam Ravnborg
2008-06-24 15:32 ` Support arch/$ARCH/include in kbuild Arnd Bergmann
2008-06-26 18:56 ` Sam Ravnborg
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=20080622220508.GA8957@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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