From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:38507)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1QYcaf-0005lQ-Iq
	for qemu-devel@nongnu.org; Mon, 20 Jun 2011 07:24:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1QYcad-0005s4-5i
	for qemu-devel@nongnu.org; Mon, 20 Jun 2011 07:24:25 -0400
Received: from mx1.redhat.com ([209.132.183.28]:8575)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1QYcac-0005rk-N0
	for qemu-devel@nongnu.org; Mon, 20 Jun 2011 07:24:22 -0400
Message-ID: <4DFF2E91.3020006@redhat.com>
Date: Mon, 20 Jun 2011 13:27:13 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
References: <BANLkTimbcu1N0DziFzc59LMqNnuTTfRhOw@mail.gmail.com>
	<2D4BBF48-D603-46F5-8793-D3F8BE09CB07@web.de>
In-Reply-To: <2D4BBF48-D603-46F5-8793-D3F8BE09CB07@web.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH 0/9] AREG0 patches
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?Andreas_F=E4rber?= <andreas.faerber@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>

Am 19.06.2011 23:55, schrieb Andreas F=E4rber:
> Am 19.06.2011 um 22:57 schrieb Blue Swirl:
>=20
>> These and the stack frame patches can be found in
>> git://repo.or.cz/qemu/blueswirl.git
>>
>> Blue Swirl (9):
>>  cpu_loop_exit: avoid using AREG0
>>  sparc: fix coding style of the area to be moved
>>  sparc: move do_interrupt to helper.c
>>  x86: use caller supplied CPUState for interrupt related stuff
>>  m68k: use caller supplied CPUState for interrupt related stuff
>>  cpu-exec: unify do_interrupt call
>>  exec.h: fix coding style and change cpu_has_work to return bool
>>  Move cpu_has_work and cpu_pc_from_tb to cpu.h
>>  Remove exec-all.h include directives
>=20
> This is getting rather unhandy with two series...
>=20
> Could you please check that chainreplyto =3D true under [sendemail]? I =
=20
> have no other related options set, and it used to work via Gmail last =20
> time I tried.

Actually, chainreply =3D false is what you want, so that all patches are
replies to patch 0 instead of patch n-1.

Of course, you need to send off the whole series with only a single
git-send-email invocation for it to work, like git send-email 00*.patch

Kevin