From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Arnd Bergmann <arnd@arndb.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New location for generic headers?
Date: Wed, 3 Dec 2008 07:21:49 -0500 [thread overview]
Message-ID: <20081203122149.GA27944@infradead.org> (raw)
In-Reply-To: <20081203121955.GJ6703@one.firstfloor.org>
On Wed, Dec 03, 2008 at 01:19:55PM +0100, Andi Kleen wrote:
> The only problem I see is that it would user space use of asm/
> without make headers_install impossible.
Well, they aren't supposed to do that anyway, so I would consider
breaking it a good idea.
next prev parent reply other threads:[~2008-12-03 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 0:36 [PATCH] Clean up namespace in kmap_types.h Andi Kleen
2008-12-03 10:40 ` Arnd Bergmann
2008-12-03 11:20 ` Andi Kleen
2008-12-03 12:13 ` Arnd Bergmann
2008-12-03 12:01 ` New location for generic headers? Sam Ravnborg
2008-12-03 12:19 ` Andi Kleen
2008-12-03 12:21 ` Christoph Hellwig [this message]
2008-12-03 12:42 ` Andi Kleen
2008-12-03 12:37 ` Christoph Hellwig
2008-12-03 12:26 ` Arnd Bergmann
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=20081203122149.GA27944@infradead.org \
--to=hch@infradead.org \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=x86@kernel.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