From: "Guan Xuetao" <guanxuetao@mprc.pku.edu.cn>
To: 'Sam Ravnborg' <sam@ravnborg.org>
Cc: 'lkml' <linux-kernel@vger.kernel.org>,
'linux-kbuild' <linux-kbuild@vger.kernel.org>,
'linux arch' <linux-arch@vger.kernel.org>,
'Arnd Bergmann' <arnd@arndb.de>, 'Michal Marek' <mmarek@suse.cz>
Subject: RE: [PATCH 1/2] kbuild: asm-generic support
Date: Tue, 11 Jan 2011 09:39:49 +0800 [thread overview]
Message-ID: <005b01cbb130$712f8f80$538eae80$@mprc.pku.edu.cn> (raw)
In-Reply-To: <20110110162639.GB13763@merkur.ravnborg.org>
> -----Original Message-----
> From: Sam Ravnborg [mailto:sam@ravnborg.org]
> Sent: Tuesday, January 11, 2011 12:27 AM
> To: Guan Xuetao
> Cc: 'lkml'; 'linux-kbuild'; 'linux arch'; 'Arnd Bergmann'; 'Michal Marek'
> Subject: Re: [PATCH 1/2] kbuild: asm-generic support
>
> Hi Guan (I will try to spell you name correct fom now on!)
Thanks.
>
> > > + During the prepare phase of the build a wrapper include
> > > + file is generated in the directory:
> > > +
> > > + arch/$(ARCH)/include/generated/asm
> > IMHO, the directory could be include/generated/asm
>
> We have moved all the arch specific files away from include/*
> which is why I invented arch/$(ARCH)/include/generated.
>
> I was actually considering:
>
> arch/$(ARCH)/generated.
>
> But using include/generated just seems wrong.
The generated headers is just the wrapper of asm-generic headers, so it's
more the interface than the arch specific files.
Using include/generated avoids two generated header dirs, and simplifies
the thought and handler.
Guan Xuetao
next prev parent reply other threads:[~2011-01-11 1:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 13:03 [RFC] kbuild: generic support for asm-generic Sam Ravnborg
2011-01-08 13:04 ` [PATCH 1/2] kbuild: asm-generic support Sam Ravnborg
2011-01-08 13:45 ` Stephen Rothwell
2011-01-08 14:03 ` Sam Ravnborg
2011-01-08 14:10 ` Guan Xuetao
2011-01-08 13:05 ` [EXAMPLE PATCH 2/2] x86: start to utilize kbuild " Sam Ravnborg
2011-01-08 20:53 ` [RFC] kbuild: generic support for asm-generic Arnd Bergmann
2011-01-08 21:33 ` Sam Ravnborg
2011-01-09 0:15 ` Arnd Bergmann
2011-01-09 8:28 ` [RFC v2] " Sam Ravnborg
2011-01-09 8:31 ` [PATCH 1/2] kbuild: asm-generic support Sam Ravnborg
2011-01-09 14:03 ` Arnd Bergmann
2011-01-09 15:10 ` Sam Ravnborg
2011-01-09 16:13 ` Arnd Bergmann
2011-01-09 8:32 ` [EXAMPLE PATCH 2/2] x86: start to utilize kbuild " Sam Ravnborg
2011-01-09 19:27 ` [RFC v3] kbuild: generic support for asm-generic Sam Ravnborg
2011-01-09 19:29 ` [PATCH 1/2] kbuild: asm-generic support Sam Ravnborg
2011-01-09 20:31 ` Arnd Bergmann
2011-01-09 21:24 ` Sam Ravnborg
2011-01-10 13:14 ` Guan Xuetao
2011-01-10 16:26 ` Sam Ravnborg
2011-01-11 1:39 ` Guan Xuetao [this message]
2011-01-10 13:31 ` Guan Xuetao
2011-01-13 16:14 ` Michal Marek
2011-01-13 17:01 ` Sam Ravnborg
2011-01-14 14:43 ` Michal Marek
2011-04-22 15:53 ` [PATCH v3] " Sam Ravnborg
2011-04-25 1:29 ` Guan Xuetao
2011-04-27 19:42 ` Sam Ravnborg
2011-04-27 19:46 ` [PATCH v4] " Sam Ravnborg
2011-04-27 19:52 ` Arnd Bergmann
2011-04-27 20:29 ` [PATCH v5] " Sam Ravnborg
2011-04-28 16:16 ` Michal Marek
2011-01-09 19:29 ` [EXAMPLE PATCH 2/2] x86: start to utilize kbuild " 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='005b01cbb130$712f8f80$538eae80$@mprc.pku.edu.cn' \
--to=guanxuetao@mprc.pku.edu.cn \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--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