From: "Jike Song" <albcamus@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Do we really need file `all'?
Date: Tue, 30 Dec 2008 17:28:08 +0800 [thread overview]
Message-ID: <df9815e70812300128h355a0018s943ecf324bceabf5@mail.gmail.com> (raw)
In-Reply-To: <20081230092401.GB27321@uranus.ravnborg.org>
On Tue, Dec 30, 2008 at 5:24 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
>
> All architectures are scehuled to move their .h files to
> arch/$ARCH/include/* in this merge window.
Good news, thanks for the clarification;-)
--
Thanks,
Jike
next prev parent reply other threads:[~2008-12-30 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 6:17 Do we really need file `all'? Jike Song
2008-12-30 7:36 ` Jike Song
2008-12-30 9:24 ` Sam Ravnborg
2008-12-30 9:28 ` Jike Song [this message]
2008-12-30 9:22 ` 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=df9815e70812300128h355a0018s943ecf324bceabf5@mail.gmail.com \
--to=albcamus@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=sam@ravnborg.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