DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hJCVtAAais+7tCNV/ayNL/IHb1GMuuAQQuhVA/fkw46R+0fk9mh3NBcYnpNyy3mJXLF8bo0DtIZ7+D/LMH3/wv+gU2c2th5OrgNsqOPe7iLVVEa2NNIzGO6oRKnKtUuwDsv2zmyU6hl7a0Fr1AdxOIeX5Ubmsyz/vx6hheOXpvk=
Message-ID: <a36005b50602070937h60e35294q1dbef2c21f2fb50d@mail.gmail.com>
Date: Tue, 7 Feb 2006 09:37:13 -0800
From: Ulrich Drepper <drepper@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Subject: Re: [PATCH 2/8] UML - Define jmpbuf access constants
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
       user-mode-linux-devel@lists.sourceforge.net
In-Reply-To: <200602070223.k172NpJa009654@ccure.user-mode-linux.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <200602070223.k172NpJa009654@ccure.user-mode-linux.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 728
Lines: 16

On 2/6/06, Jeff Dike <jdike@addtoit.com> wrote:
> With newer libcs, the JB_* macros (which we shouldn't be using anyway,
> probably) go away.

I assume you have your own setjmp implementation and are not using the
libc version?

If you don't then there is a problem.  There is a good reason why the
constants are removed: you couldn't use the values anyway.  Your don't
have the information to "decrypt" them.  If you just used the values
and implemented the function yourself, fine.
-
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/