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: Sun, 22 Jun 2008 00:11:37 +0200 [thread overview]
Message-ID: <20080621221137.GD12279@uranus.ravnborg.org> (raw)
In-Reply-To: <20080621220703.GA12279@uranus.ravnborg.org>
>
> Patches are on top of kbuild-next.git and follows.
Just to make it crystal clear.
These patches are for comment and I will await feedback before
pushing to kbuild-next.git (and thus -next).
And archs are not forced to move their header files now.
They can wait until it fits their schedule.
Sam
next prev parent reply other threads:[~2008-06-21 22:10 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 ` Sam Ravnborg [this message]
2008-06-22 22:05 ` Support arch/$ARCH/include in kbuild Sam Ravnborg
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=20080621221137.GD12279@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