From: Alexander Graf <agraf@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/3] spapr: fix H_SET_MODE
Date: Tue, 11 Feb 2014 13:12:24 +0100 [thread overview]
Message-ID: <52FA13A8.3040100@suse.de> (raw)
In-Reply-To: <52F9D4D6.7070002@ozlabs.ru>
On 02/11/2014 08:44 AM, Alexey Kardashevskiy wrote:
> On 01/22/2014 04:43 PM, Alexey Kardashevskiy wrote:
>> This fixes H_SET_MODE.
>>
>> Alexey Kardashevskiy (3):
>> target-ppc: introduce powerisa-207-server flag
>> spapr-hcall: fix little-endian resource handling in H_SET_MODE
>> spapr-hcall: add address-translation-mode-on-interrupt resource in
>> H_SET_MODE
>>
>> hw/ppc/spapr_hcall.c | 64 +++++++++++++++++++++++++++++++++++++++------
>> include/hw/ppc/spapr.h | 9 +++++--
>> target-ppc/cpu.h | 4 +++
>> target-ppc/translate_init.c | 3 ++-
>> 4 files changed, 69 insertions(+), 11 deletions(-)
> Ping?
Why are you pinging? There were review comments on this patch set, no?
Alex
next prev parent reply other threads:[~2014-02-11 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 5:43 [Qemu-devel] [PATCH v3 0/3] spapr: fix H_SET_MODE Alexey Kardashevskiy
2014-01-22 5:43 ` [Qemu-devel] [PATCH v3 1/3] target-ppc: introduce powerisa-207-server flag Alexey Kardashevskiy
2014-01-22 5:43 ` [Qemu-devel] [PATCH v3 2/3] spapr-hcall: fix little-endian resource handling in H_SET_MODE Alexey Kardashevskiy
2014-01-22 5:43 ` [Qemu-devel] [PATCH v3 3/3] spapr-hcall: add address-translation-mode-on-interrupt resource " Alexey Kardashevskiy
2014-01-23 8:26 ` Aneesh Kumar K.V
2014-02-11 7:44 ` Alexey Kardashevskiy
2014-02-11 7:44 ` [Qemu-devel] [PATCH v3 0/3] spapr: fix H_SET_MODE Alexey Kardashevskiy
2014-02-11 12:12 ` Alexander Graf [this message]
2014-02-11 12:16 ` Alexey Kardashevskiy
2014-02-14 9:30 ` Alexey Kardashevskiy
2014-03-07 4:01 ` Alexey Kardashevskiy
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=52FA13A8.3040100@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).