From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1J3sUy-00087f-AQ
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 07:21:36 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1J3sUw-00086M-Dx
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 07:21:35 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1J3sUw-000868-88
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 07:21:34 -0500
Received: from ug-out-1314.google.com ([66.249.92.169])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <balrogg@gmail.com>) id 1J3sUv-0003Ii-TJ
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 07:21:34 -0500
Received: by ug-out-1314.google.com with SMTP id m2so1486492uge.4
	for <qemu-devel@nongnu.org>; Sun, 16 Dec 2007 04:21:31 -0800 (PST)
Message-ID: <fb249edb0712160421s777b587bvb86fe935687af1a6@mail.gmail.com>
Date: Sun, 16 Dec 2007 13:21:30 +0100
From: "andrzej zaborowski" <balrogg@gmail.com>
Subject: Re: [Qemu-devel] [Patch 1/2v2][PXA27x] initial keypad support
In-Reply-To: <47609EF8.6020606@kama-aina.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47609EF8.6020606@kama-aina.net>
Reply-To: qemu-devel@nongnu.org
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: qemu-devel@nongnu.org

On 13/12/2007, Armin <akuster@kama-aina.net> wrote:
> Hello,
> Here is a new series of keypad support patches for the PXA27x.
> I believe I have addressed all the concerns from my first set of patch.

Thanks! I just changed the use of cpu_abort to an exit() because
cpu_single_env will typically be NULL at the time of initialisation.
Please test.
Cheers