qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Liu Jinsong <jinsong.liu@intel.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, Nicholas Piggin <npiggin@gmail.com>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	qemu-ppc@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr
Date: Mon, 22 Jul 2019 21:42:03 +1000	[thread overview]
Message-ID: <20190722114203.GI25073@umbus.fritz.box> (raw)
In-Reply-To: <585a8a2b-6ed2-dd44-bc38-7669f0357528@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

On Mon, Jul 22, 2019 at 01:20:08PM +0200, Paolo Bonzini wrote:
> On 22/07/19 10:39, David Gibson wrote:
> > On Mon, Jul 22, 2019 at 03:32:12PM +1000, Nicholas Piggin wrote:
> >> Hi, this series is rebased on top of the qmp event fix, and takes
> >> Paolo's suggestion to implement ->wakeup for i386 before adding
> >> ppc, which makes it much nicer.
> >>
> >> If the first two patches can be agreed on initially and merged, I
> >> can take the third patch through the ppc list after that.
> > 
> > LGTM.  Now, what tree(s) do we merge this through?
> 
> I have just spotted a volunteer!

Well, merging an i386 patch through the ppc tree is kinda weird, but
yeah, I can do that.
> 
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> Paolo
> 
> >>
> >> Thanks,
> >> Nick
> >>
> >> Nicholas Piggin (3):
> >>   machine: Add wakeup method to MachineClass
> >>   i386: use machine class ->wakeup method
> >>   spapr: Implement ibm,suspend-me
> >>
> >>  hw/i386/pc.c           |  8 ++++++++
> >>  hw/ppc/spapr.c         |  7 +++++++
> >>  hw/ppc/spapr_rtas.c    | 32 ++++++++++++++++++++++++++++++++
> >>  include/hw/boards.h    |  1 +
> >>  include/hw/ppc/spapr.h |  3 ++-
> >>  vl.c                   | 16 +++++++++++++++-
> >>  6 files changed, 65 insertions(+), 2 deletions(-)
> >>
> > 
> 

-- 
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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-22 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  5:32 [Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr Nicholas Piggin
2019-07-22  5:32 ` [Qemu-devel] [PATCH v2 1/3] machine: Add wakeup method to MachineClass Nicholas Piggin
2019-07-22  8:38   ` David Gibson
2019-07-22  8:39 ` [Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr David Gibson
2019-07-22 11:20   ` Paolo Bonzini
2019-07-22 11:42     ` David Gibson [this message]
2019-07-23  3:40     ` David Gibson
  -- strict thread matches above, loose matches on Subject: below --
2019-07-22  5:19 Nicholas Piggin

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=20190722114203.GI25073@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=jinsong.liu@intel.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mst@redhat.com \
    --cc=npiggin@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    /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).