All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Fam Zheng <famz@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org,
	Alistair Francis <alistair.francis@xilinx.com>,
	qemu-arm@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
	Subbaraya Sundeep <sundeep.lkml@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] msf2: drop cpu_model to directly use cpu type
Date: Tue, 19 Sep 2017 06:48:55 -0300	[thread overview]
Message-ID: <f8cc735e-3f23-5a0c-4e31-d253111fcee0@amsat.org> (raw)
In-Reply-To: <20170919020837.GA11534@lemon.lan>

On 09/18/2017 11:08 PM, Fam Zheng wrote:
> On Mon, 09/18 19:11, Philippe Mathieu-Daudé wrote:
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>> after Igor comment:
>> http://lists.nongnu.org/archive/html/qemu-devel/2017-09/msg04709.html
>>
>> Fam: I'm trying your patchew "apply over series" feature on these 2 series,
>>       hoping they get both applied before my patch:
>>
>> Based-on: 1505318697-77161-6-git-send-email-imammedo@redhat.com
>> Based-on: 1505762601-27143-6-git-send-email-sundeep.lkml@gmail.com
> 
> Only one based-on will be picked up, so this doesn't work. Patchew basically
> applies the series on top of something, where something is the result of a
> previous applying. So it can be thought of a chain.

OK, here I used each series trail, luckily they apply independently.
It seems your script only kept/used then last Based-on.

> 
> To support multiple patches, a different approach needs to be implemented.
> 
> Fam
> 

      reply	other threads:[~2017-09-19  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 22:11 [Qemu-devel] [PATCH] msf2: drop cpu_model to directly use cpu type Philippe Mathieu-Daudé
2017-09-19  2:08 ` Fam Zheng
2017-09-19  9:48   ` Philippe Mathieu-Daudé [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=f8cc735e-3f23-5a0c-4e31-d253111fcee0@amsat.org \
    --to=f4bug@amsat.org \
    --cc=alistair.francis@xilinx.com \
    --cc=ehabkost@redhat.com \
    --cc=famz@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sundeep.lkml@gmail.com \
    /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.