DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=received:message-id:date:from:to:subject:in-reply-to:
	mime-version:content-type:content-transfer-encoding:
	content-disposition:references;
	b=rFf3CBxWNQHBP2QAOI7BBnXiC63yvTjM0tWGxog+hgPHzzDl01pf1NSs+SGtRF5cM
	Xba8zQkyjcDi0bXtGJZVA==
Message-ID: <545d88bc0603101553i3cd98368y8e9f9b2f79d294ce@mail.google.com>
Date: Fri, 10 Mar 2006 15:53:56 -0800
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
In-Reply-To: <20060310234010.GA6549@nevyn.them.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <4410BB32.1020905@google.com>
	 <20060309184759.591e3551.akpm@osdl.org> <4410EC8A.4020808@google.com>
	 <20060309192232.2fd4767c.akpm@osdl.org>
	 <545d88bc0603091936i5c25c065ne8e31ca23e9473f4@mail.google.com>
	 <20060310234010.GA6549@nevyn.them.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 920
Lines: 20

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/