From: Alexander Graf <agraf@suse.de>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Andreas Färber" <afaerber@suse.de>,
bharata@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v4 0/4] little-endian dump for ppc64
Date: Mon, 19 May 2014 22:11:14 +0200 [thread overview]
Message-ID: <537A6562.8020408@suse.de> (raw)
In-Reply-To: <20140519174410.27382.38486.stgit@bahia.local>
On 19.05.14 19:57, Greg Kurz wrote:
> Hi,
>
> Here are latest bits I have to support ppc64le guest dumps.
> Changes since v3 are:
> - fixed altivec registers support (patch 2)
> - kicked "virtio" out of the descriton of patch 3 since
> it won't rely on LPCR_ILE
>
> The other two patches are unchanged. I resend the whole patch set in case Alex
> feels like applying it right away :P
I've changed the subject line of patch 3/4 to
target-ppc: Introduce callback for interrupt endianness
to make it more clear what the patch is doing. I've also fixed up patch
1/4 to apply on current master.
Thanks, applied to ppc-next.
Alex
prev parent reply other threads:[~2014-05-19 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 17:57 [Qemu-devel] [PATCH v4 0/4] little-endian dump for ppc64 Greg Kurz
2014-05-19 17:57 ` [Qemu-devel] [PATCH v4 1/4] dump: Make DumpState and endian conversion routines available for arch-specific dump code Greg Kurz
2014-05-19 17:58 ` [Qemu-devel] [PATCH v4 2/4] target-ppc: Support dump for little endian ppc64 Greg Kurz
2014-05-19 17:59 ` [Qemu-devel] [PATCH v4 3/4] target-ppc: ppc can be either endian Greg Kurz
2014-05-19 17:59 ` [Qemu-devel] [PATCH v4 4/4] target-ppc: Set the correct endianness in ELF dump header Greg Kurz
2014-05-19 20:11 ` Alexander Graf [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=537A6562.8020408@suse.de \
--to=agraf@suse.de \
--cc=afaerber@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--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).