From: Sam Ravnborg <sam@ravnborg.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
linux arch <linux-arch@vger.kernel.org>,
Guan Xuetao <guanxuetao@mprc.pku.edu.cn>,
Michal Marek <mmarek@suse.cz>
Subject: Re: [RFC] kbuild: generic support for asm-generic
Date: Sat, 8 Jan 2011 22:33:53 +0100 [thread overview]
Message-ID: <20110108213353.GA24666@merkur.ravnborg.org> (raw)
In-Reply-To: <201101082153.31837.arnd@arndb.de>
On Sat, Jan 08, 2011 at 09:53:31PM +0100, Arnd Bergmann wrote:
> On Saturday 08 January 2011, Sam Ravnborg wrote:
> > Hi Arnd et all.
> >
> > This is my second attempt to provide generic support for
> > architectures that use existing headers from asm-generic.
> >
> > With this kbuild will read the file: arch/$ARCH/include/asm-generic
> >
> > For each file listed in this file a wrapper is generated in
> > arch/$ARCH/inclue/generated/asm/
> >
> > The patch include support so headers_install works.
> >
> > The inspiration came from the unicore32 patchset,
> > but I redid this to make it more general.
> >
> > I will follow-up with two patches.
> > One that implment the functionality.
> > A second that convert two headers in x86 to use the
> > new asm-generic stuff (only as an example).
>
> Very nice patch!
>
> This is something I'd certainly like to see upstream, and you made
> a good point about keeping it seperate from the unicore32 submission.
>
> One detail I don't like too much is that you now have two different
> formats for specifying lists of headers to do something with.
>
> Instead of the new arch/*/include/asm-generic file, how about listing
> all files that are actually provided by the architecture as "header-y"
> in arch/*/include/asm/Kbuild, and listing all files as something
> else in include/asm-generic/Kbuild and include/asm-generic/Kbuild.asm?
Good point.
I will try to address this together with the comments from Guang.
If we use Kbuild syntax then I think we shall name the file
something like
Kbuild.asm-generic
I need to think about the naming of the variables...
We need a variables to express:
In include/asm-generic/Kbuild.asm
- This file exists in a generic variant and it is exported.
The arch may use it verbatim or may have a local variant
In arch/$(ARCH)/include/Kbuild.asm-generic
- This file is provided verbatim by asm-generic
Something like:
export-y - for files listed in Kbuild.asm
generic-y - for files listed in Kbuild.asm-generic
I will try to come up with a patch that uses this - or something
similar.
Sam
next prev parent reply other threads:[~2011-01-08 21:33 UTC|newest]
Thread overview: 58+ 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:03 ` Sam Ravnborg
2011-01-08 13:04 ` [PATCH 1/2] kbuild: asm-generic support Sam Ravnborg
2011-01-08 13:04 ` Sam Ravnborg
2011-01-08 13:45 ` Stephen Rothwell
2011-01-08 14:03 ` Sam Ravnborg
2011-01-08 14:03 ` Sam Ravnborg
2011-01-08 14:10 ` Guan Xuetao
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 13:05 ` Sam Ravnborg
2011-01-08 20:53 ` [RFC] kbuild: generic support for asm-generic Arnd Bergmann
2011-01-08 21:33 ` Sam Ravnborg [this message]
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:28 ` Sam Ravnborg
2011-01-09 8:31 ` [PATCH 1/2] kbuild: asm-generic support Sam Ravnborg
2011-01-09 8:31 ` 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 16:13 ` Arnd Bergmann
2011-01-09 8:32 ` [EXAMPLE PATCH 2/2] x86: start to utilize kbuild " Sam Ravnborg
2011-01-09 8:32 ` Sam Ravnborg
2011-01-09 19:27 ` [RFC v3] kbuild: generic support for asm-generic Sam Ravnborg
2011-01-09 19:27 ` Sam Ravnborg
2011-01-09 19:29 ` [PATCH 1/2] kbuild: asm-generic support Sam Ravnborg
2011-01-09 19:29 ` Sam Ravnborg
2011-01-09 20:31 ` Arnd Bergmann
2011-01-09 20:31 ` Arnd Bergmann
2011-01-09 21:24 ` Sam Ravnborg
2011-01-09 21:24 ` Sam Ravnborg
2011-01-10 13:14 ` Guan Xuetao
2011-01-10 13:14 ` Guan Xuetao
2011-01-10 16:26 ` Sam Ravnborg
2011-01-10 16:26 ` Sam Ravnborg
2011-01-11 1:39 ` Guan Xuetao
2011-01-10 13:31 ` Guan Xuetao
2011-01-10 13:31 ` Guan Xuetao
2011-01-13 16:14 ` Michal Marek
2011-01-13 17:01 ` Sam Ravnborg
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-22 15:53 ` Sam Ravnborg
2011-04-25 1:29 ` Guan Xuetao
2011-04-27 19:42 ` Sam Ravnborg
2011-04-27 19:42 ` Sam Ravnborg
2011-04-27 19:46 ` [PATCH v4] " Sam Ravnborg
2011-04-27 19:46 ` Sam Ravnborg
2011-04-27 19:52 ` Arnd Bergmann
2011-04-27 19:52 ` Arnd Bergmann
2011-04-27 20:29 ` [PATCH v5] " Sam Ravnborg
2011-04-27 20:29 ` 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
2011-01-09 19:29 ` 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=20110108213353.GA24666@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=arnd@arndb.de \
--cc=guanxuetao@mprc.pku.edu.cn \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).