From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Lynch Subject: Re: [PATCH] use correct ccr bit for syscall error status Date: Fri, 12 Mar 2010 12:57:03 -0600 Message-ID: <1268420223.3763.35.camel@localhost.localdomain> References: <1268418393-18325-1-git-send-email-ntl@pobox.com> <1268418393-18325-2-git-send-email-ntl@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1268418393-18325-2-git-send-email-ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Oren Laadan Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: containers.vger.kernel.org On Fri, 2010-03-12 at 12:26 -0600, Nathan Lynch wrote: > The powerpc implementations of syscall_get_error and > syscall_set_return_value should use CCR0:S0 (0x10000000) for testing > and setting syscall error status. Fortunately these APIs don't seem > to be used at the moment. I'll be sending this to the powerpc maintainer as well, so hopefully we don't have to carry it for too long.