From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Marek <mmarek@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>,
linux-kbuild@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC] possible killing of boilerplate headers by asm-generic reorg
Date: Thu, 11 Aug 2011 15:16:43 +0200 [thread overview]
Message-ID: <201108111516.44243.arnd@arndb.de> (raw)
In-Reply-To: <CA+55aFy9_menekFnwEPFVYb493m-_77HibPL4VXfd6-Jh4rzLA@mail.gmail.com>
On Wednesday 10 August 2011, Linus Torvalds wrote:
> Or you can do it by creating the default file, and then editing EVERY
> SINGLE ARCHITECTURE. Which just sucks.
>
> This has come up before, for similar situations - wanting to implement
> optional architecture capabilities without having to worry about
> architectures that don't support it.
If you mostly care about new extensions, we can ignore all the
user ABI headers for now and find a solution that just deals with
the kernel internal ones.
I think the easiest way to do that would be to move all non-exported
headers from include/asm-generic to include/asm. Since it's only about
internel users then, we can simply use "#include_next <asm/foo.h>"
to refer to them from arch-specific files that want to reuse them
only partially and also add some of their own definitions.
Arnd
next prev parent reply other threads:[~2011-08-11 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 20:41 [RFC] possible killing of boilerplate headers by asm-generic reorg Al Viro
2011-08-07 21:00 ` Linus Torvalds
2011-08-10 9:52 ` Michal Marek
2011-08-10 12:20 ` Arnd Bergmann
2011-08-10 15:34 ` Linus Torvalds
2011-08-11 13:16 ` Arnd Bergmann [this message]
2011-08-11 13:25 ` Al Viro
2011-08-11 14:20 ` David Howells
2011-08-11 20:44 ` Sam Ravnborg
2011-08-11 14:25 ` 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=201108111516.44243.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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