mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: dkegel <dkegel@google.com>
To: dkegel <dkegel@google.com>, "Andrew Morton" <akpm@osdl.org>,
	"Markus Gutschke" <markus@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Make _syscallX() macros compile in PIC mode on i386
Date: Fri, 10 Mar 2006 15:53:56 -0800	[thread overview]
Message-ID: <545d88bc0603101553i3cd98368y8e9f9b2f79d294ce@mail.google.com> (raw)
In-Reply-To: <20060310234010.GA6549@nevyn.them.org>

On 3/10/06, Daniel Jacobowitz <dan@debian.org> wrote:
> > I'd like to see these patches go in to the sanitized kernel headers
> > and/or the kernel.org tree.  I imagine that putting them in the kernel.org
> > tree is right, and they'd naturally percolate from there to the
> > various sanitized headers projects.
>
> It uses the headers for many things.  It does not use the _syscallX
> macros.

Sorry, I misspoke.
The glibc build process makes the _syscallX macros available
to userspace via the <asm/syscalls.h> include.
So even if glibc doesn't use those macros directly,
it does seem to pass them along.  Which is how
Markus got on to this whole topic in the first place.

  reply	other threads:[~2006-03-10 23:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 23:33 Markus Gutschke
2006-03-10  2:47 ` Andrew Morton
2006-03-10  3:03   ` Markus Gutschke
2006-03-10  3:22     ` Andrew Morton
2006-03-10  3:36       ` dkegel
2006-03-10 23:40         ` Daniel Jacobowitz
2006-03-10 23:53           ` dkegel [this message]
2006-03-10 22:42       ` [PATCH 1/1] x86: Make _syscallX() macros compile in PIC mode on i386 (updated patch) Markus Gutschke
2006-03-10 23:02         ` dkegel
2006-03-11  0:05       ` [PATCH 1/1] x86: Make _syscallX() macros compile in PIC mode on i386 Arnd Bergmann
2006-03-10 14:37   ` Jan Engelhardt

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=545d88bc0603101553i3cd98368y8e9f9b2f79d294ce@mail.google.com \
    --to=dkegel@google.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@google.com \
    /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

all inboxes | Powered by JetHome®