public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [RFC] possible killing of boilerplate headers by asm-generic reorg
Date: Wed, 10 Aug 2011 11:52:33 +0200	[thread overview]
Message-ID: <4E4254E1.5070909@suse.cz> (raw)
In-Reply-To: <CA+55aFxSOio5efktO+fQOL6qEaE2KBFyCcOcvNMOvWGpY-ktiQ@mail.gmail.com>

On 7.8.2011 23:00, Linus Torvalds wrote:
> However, having it for the default case for those full header files is
> just annoying - as you say, those idiotic one-liner <asm/bar.h> files
> that just include the asm-generic one are annoying, and quite frankly,
> the current work-around for them (that "generic-y" thing) is not
> really any better. It's just another way to do the same broken thing.

It replaces oneline files with a multiline list in a single file, so it
makes no difference linewise, but at least one arch has it all in a
single place.


> So I would suggest we just start a new directory, something like
> include/default, and add it as the last entry to the search path. Then
> we start populating it with <asm/xyz.h> files, and start removing the
> silly 'generic-y' workaround. Let's just use the search-path instead.

But we would still have to generate the wrapper for userspace headers,
we can't rely on any -I/usr/include/default in userspace. So
Makefile.headersinst would still need some special handling for these
headers.

Michal

  reply	other threads:[~2011-08-10  9:52 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 [this message]
2011-08-10 12:20     ` Arnd Bergmann
2011-08-10 15:34     ` Linus Torvalds
2011-08-11 13:16       ` Arnd Bergmann
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=4E4254E1.5070909@suse.cz \
    --to=mmarek@suse.cz \
    --cc=arnd@arndb.de \
    --cc=linux-kbuild@vger.kernel.org \
    --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