From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MdNJy-00053E-0C
	for qemu-devel@nongnu.org; Tue, 18 Aug 2009 07:57:46 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MdNJt-000508-0e
	for qemu-devel@nongnu.org; Tue, 18 Aug 2009 07:57:45 -0400
Received: from [199.232.76.173] (port=38141 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MdNJs-000505-St
	for qemu-devel@nongnu.org; Tue, 18 Aug 2009 07:57:40 -0400
Received: from dd21438.kasserver.com ([85.13.141.110]:49670)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <martin.mohring@opensuse.org>) id 1MdNJs-00013g-Ck
	for qemu-devel@nongnu.org; Tue, 18 Aug 2009 07:57:40 -0400
Message-ID: <4A8A94DB.3000508@opensuse.org>
Date: Tue, 18 Aug 2009 13:47:39 +0200
From: Martin Mohring <martin.mohring@opensuse.org>
MIME-Version: 1.0
References: <4A86D927.2090601@opensuse.org> <20090817183006.GA4433@kos.to>
	<200908181132.06977.uli@suse.de>
In-Reply-To: <200908181132.06977.uli@suse.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH 1/1] Corrected Version of uid16 fix for
	PowerPC
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Ulrich Hecht <uli@suse.de>
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org

Ulrich Hecht wrote:
> On Monday 17 August 2009, Riku Voipio wrote:
>   
>> If the patch below supposed to supercede the s390x patch, shouldn't
>> this enable UID16 on s390x as well?
>>     
>
> I don't see how this patch relates to mine at all, really. Either way, 
> enabling UID16 on s390x would be incorrect.
>
> CU
> Uli
>
>   
OK. I thought that enabling the uid16 *calls* needs also to enable the
uid16 *conversions* because otherwise the calls cannot work.
Maybe i am wrong? That was why i activated the uid16 conversion on PPC
together with uid16 calls. I tested this with
Debian PPC 32 bit targets....

Martin