qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: "aliguori@us.ibm.com" <aliguori@us.ibm.com>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [0/6] Pending pseries updates
Date: Thu, 27 Sep 2012 20:29:03 +1000	[thread overview]
Message-ID: <20120927102903.GB24942@truffula.fritz.box> (raw)
In-Reply-To: <B0768CBC-5960-4F01-8DDF-D80408869C47@suse.de>

On Thu, Sep 27, 2012 at 10:05:48AM +0200, Alexander Graf wrote:
> 
> 
> On 27.09.2012, at 01:31, David Gibson <dwg@au1.ibm.com> wrote:
> 
> > On Wed, Sep 26, 2012 at 02:59:25PM +0200, Alexander Graf wrote:
> >> 
> >> On 26.09.2012, at 05:12, David Gibson wrote:
> >> 
> >>> Hi Alex,
> >>> 
> >>> Here's another batch of updates for pseries, some of which affect
> >>> wider target-ppc code.  I have sent a few of these before, but I don't
> >>> believe any have made it into ppc-next so far.  5/6 is an important
> >>> bugfix we've discussed before, which I've CCed to qemu-stable.
> >> 
> >> Thanks, applied 1/5, 2/6, 5/6, 6/6.
> >> 
> >> 4/6 still needs fixing for TCG. Please compile QEMU with --enable-debug-tcg to see the warnings emerging from your change :).
> >> 5/6 still has a comment in flight.
> > 
> > Uh, I assume you mean 3/6 and 4/6 here rather than 4/6 and 5/6.
> 
> Of course :). I'm just bad with numbers ;).
> 
> Btw, when running git format-patch to get patch files from your
> tree, try passing --cover-letter to it for a nice patch set summary
> :)

I don't generally use git format-patch directly, I use git sent-email
--compose.


-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

      reply	other threads:[~2012-09-27 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26  3:12 [Qemu-devel] [0/6] Pending pseries updates David Gibson
2012-09-26  3:12 ` [Qemu-devel] [PATCH 1/6] pseries: Set hash table size based on RAM size David Gibson
2012-09-26  3:12 ` [Qemu-devel] [PATCH 2/6] target-ppc: Remove unused power_mode field from cpu state David Gibson
2012-09-26  3:12 ` [Qemu-devel] [PATCH 3/6] target-ppc: Extend FPU state for newer POWER CPUs David Gibson
2012-09-26  6:36   ` Aurelien Jarno
2012-09-27  0:03     ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-09-26  3:12 ` [Qemu-devel] [PATCH 4/6] pseries: Implement PAPR NVRAM David Gibson
2012-09-26 12:55   ` Alexander Graf
2012-09-26 21:25     ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2012-09-26  3:12 ` [Qemu-devel] [PATCH 5/6] pseries: Don't test for MSR_PR for hypercalls under KVM David Gibson
2012-09-26  3:12 ` [Qemu-devel] [PATCH 6/6] ppc/pseries: Reset VPA registration on CPU reset David Gibson
2012-09-26 12:59 ` [Qemu-devel] [0/6] Pending pseries updates Alexander Graf
2012-09-26 23:31   ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-09-27  8:05     ` Alexander Graf
2012-09-27 10:29       ` David Gibson [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=20120927102903.GB24942@truffula.fritz.box \
    --to=dwg@au1.ibm.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.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).