From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] updated asm-sparc/{processor,signal,sigcontext}.h to behave nicely in userland
Date: Tue, 28 Dec 2004 03:06:57 +0000 [thread overview]
Message-ID: <20041228030657.GI771@holomorphy.com> (raw)
In-Reply-To: <1102503203.20234.7.camel@cid.outersquare.org>
On Sat, 11 Dec 2004 16:06:39 -0800 Jeremy Huddleston <eradicator@gentoo.org> wrote:
>> In changing from the glibc check to __KERNEL__, processor.h doesn't work
>> for some userland code. Here's an update to correct this.
On Mon, Dec 27, 2004 at 06:38:52PM -0800, David S. Miller wrote:
> I don't think this is too pleasant.
> Actually, I can't see much of anything that userland needs to get
> at inside of processor.h, so why don't you just __KERNEL__ ifdef
> out nearly the entire file?
I'm vaguely disinclined to take fixes for userspace inclusion of
kernel headers unless, say, other arches are taking such steps and
we would only penalize ourselves by not doing so.
By and large I'd prefer to discourage userspace code from using
kernel headers. Does this work in a significant number of other
arches as things stand now?
-- wli
next prev parent reply other threads:[~2004-12-28 3:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 10:53 [PATCH] updated asm-sparc/{processor,signal,sigcontext}.h to Jeremy Huddleston
2004-12-09 5:01 ` David S. Miller
2004-12-09 5:25 ` David S. Miller
2004-12-09 5:25 ` Jeremy Huddleston
2004-12-09 6:00 ` Jeremy Huddleston
2004-12-09 7:46 ` David S. Miller
2004-12-12 0:06 ` Jeremy Huddleston
2004-12-28 2:38 ` David S. Miller
2004-12-28 3:06 ` William Lee Irwin III [this message]
2004-12-28 3:27 ` David S. Miller
2004-12-28 3:33 ` Jeremy Huddleston
2004-12-28 6:16 ` [PATCH] updated asm-sparc/{processor,signal,sigcontext}.h to behave nicely in userland William Lee Irwin III
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=20041228030657.GI771@holomorphy.com \
--to=wli@holomorphy.com \
--cc=sparclinux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.