From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: + git-hdrcleanup-vs-git-klibc-on-ia64.patch added to -mm tree
Date: Sun, 14 May 2006 21:15:55 +0000 [thread overview]
Message-ID: <20060514211555.GA25945@infradead.org> (raw)
In-Reply-To: <1147632661.2551.5.camel@shinybook.infradead.org>
On Sun, May 14, 2006 at 07:51:00PM +0100, David Woodhouse wrote:
> On Sun, 2006-05-14 at 10:54 -0700, akpm@osdl.org wrote:
> > diff -puN include/asm/gcc_intrin.h~git-hdrcleanup-vs-git-klibc-on-ia64
> > include/asm/gcc_intrin.h
> > ---
> > 25/include/asm/gcc_intrin.h~git-hdrcleanup-vs-git-klibc-on-ia64 Mon May 15 01:33:00 2006
> > +++ 25-akpm/include/asm/gcc_intrin.h Mon May 15 01:33:00 2006
> > @@ -24,7 +24,9 @@
> > extern void ia64_bad_param_for_setreg (void);
> > extern void ia64_bad_param_for_getreg (void);
> >
> > +#ifdef __KERNEL__
> > register unsigned long ia64_r13 asm ("r13") __attribute_used__;
> > +#endif
>
> There's more than just that in asm-ia64/intrinsics.h that shouldn't be
> visible to userspace. In fact I'm not entirely sure how much of
> intrinsics.h _does_ make sense for userspace at all.
>
> What does asm-ia64/byteorder.h include it for?
Using byte swizzling instrincts I supposed. On the other hand asm/byteorder.h
really shouldn't be user-exposed to start with.
next prev parent reply other threads:[~2006-05-14 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 18:51 + git-hdrcleanup-vs-git-klibc-on-ia64.patch added to -mm tree David Woodhouse
2006-05-14 21:15 ` Christoph Hellwig [this message]
2006-05-14 21:35 ` David Woodhouse
2006-05-14 22:02 ` H. Peter Anvin
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=20060514211555.GA25945@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox