qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>, qemu-devel@nongnu.org
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
	'Shlomo Pongratz' <shlomopongratz@gmail.com>,
	'Christoffer Dall' <christoffer.dall@linaro.org>,
	'Shlomo Pongratz' <shlomo.pongratz@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/9] GIC-500 implementation, software + KVM
Date: Tue, 07 Jul 2015 15:27:38 +0200	[thread overview]
Message-ID: <559BD3CA.8050603@linaro.org> (raw)
In-Reply-To: <02a201d0b8b2$c6355da0$52a018e0$@samsung.com>

On 07/07/2015 02:45 PM, Pavel Fedin wrote:
>> do you plan to resend a version without TCG code, just using shared base
>> class?
> 
>  Done that, you missed it:
>  http://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg00830.html

Hum OK thanks. I will review that one then ;-)

Eric
> 
>  Sorry for confusion with version numbers, i have to idea how to do this correctly when
> combining/splitting different series. I set that one to v2 because i consider it to be a
> continuation of my old RFC which was v1.
> 
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
> 
> 

  reply	other threads:[~2015-07-07 13:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 14:13 [Qemu-devel] [PATCH v4 0/9] GIC-500 implementation, software + KVM Pavel Fedin
2015-07-02 14:13 ` [Qemu-devel] [PATCH v4 1/9] Implement GIC-500 base class Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 2/9] Implement GIC-500 Pavel Fedin
2015-07-02 14:19   ` Peter Maydell
2015-07-02 14:39     ` Pavel Fedin
2015-07-02 14:42       ` Peter Maydell
2015-07-02 14:45         ` Peter Maydell
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 3/9] GICv3 support Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 4/9] Add virt-v3 machine that uses GIC-500 Pavel Fedin
2015-07-02 14:25   ` Daniel P. Berrange
2015-07-02 14:47     ` Pavel Fedin
2015-07-02 15:06       ` Christoffer Dall
2015-07-02 15:30         ` Pavel Fedin
2015-07-02 15:54           ` Christoffer Dall
2015-07-03  6:52             ` Pavel Fedin
2015-07-03  7:42               ` Christoffer Dall
2015-07-03  8:47                 ` Pavel Fedin
2015-07-03 10:23                   ` Christoffer Dall
2015-07-02 16:21       ` Daniel P. Berrange
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 5/9] Extract some reusable vGIC code Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 6/9] Set kernel_irqchip_type for the rest of ARM boards which use GIC Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 7/9] Make use of kernel_irqchip_type in kvm_arch_irqchip_create() Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 8/9] Initial implementation of vGICv3 Pavel Fedin
2015-07-02 14:14 ` [Qemu-devel] [PATCH v4 9/9] Enable KVM acceleration for GICv3 Pavel Fedin
2015-07-07 10:20 ` [Qemu-devel] [PATCH v4 0/9] GIC-500 implementation, software + KVM Eric Auger
2015-07-07 12:45   ` Pavel Fedin
2015-07-07 13:27     ` Eric Auger [this message]
2015-07-07 14:15       ` Pavel Fedin

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=559BD3CA.8050603@linaro.org \
    --to=eric.auger@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --cc=p.fedin@samsung.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    --cc=shlomopongratz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).