All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/9] AREG0 patches
Date: Mon, 20 Jun 2011 13:27:13 +0200	[thread overview]
Message-ID: <4DFF2E91.3020006@redhat.com> (raw)
In-Reply-To: <2D4BBF48-D603-46F5-8793-D3F8BE09CB07@web.de>

Am 19.06.2011 23:55, schrieb Andreas Färber:
> Am 19.06.2011 um 22:57 schrieb Blue Swirl:
> 
>> 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
> 
> This is getting rather unhandy with two series...
> 
> Could you please check that chainreplyto = true under [sendemail]? I  
> have no other related options set, and it used to work via Gmail last  
> time I tried.

Actually, chainreply = 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

      reply	other threads:[~2011-06-20 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 20:57 [Qemu-devel] [PATCH 0/9] AREG0 patches Blue Swirl
2011-06-19 21:55 ` Andreas Färber
2011-06-20 11:27   ` Kevin Wolf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DFF2E91.3020006@redhat.com \
    --to=kwolf@redhat.com \
    --cc=andreas.faerber@web.de \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.