From: Stefan Hajnoczi <stefanha@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: peter.maydell@linaro.org, agraf@suse.de,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/1] ppc-for-2.8 queue 20161201
Date: Thu, 1 Dec 2016 13:39:34 +0000 [thread overview]
Message-ID: <20161201133934.GJ10441@stefanha-x1.localdomain> (raw)
In-Reply-To: <20161201044441.14365-1-david@gibson.dropbear.id.au>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Thu, Dec 01, 2016 at 03:44:40PM +1100, David Gibson wrote:
> The following changes since commit 1cd56fd2e14f67ead2f0458b4ae052f19865c41c:
>
> Update version for v2.8.0-rc2 release (2016-11-29 22:26:25 +0000)
>
> are available in the git repository at:
>
> git://github.com/dgibson/qemu.git tags/ppc-for-2.8-20161201
>
> for you to fetch changes up to 5c0139a8c2f01e068c96d456ecf12b0eeb707660:
>
> spapr: fix default DRC state for coldplugged LMBs (2016-12-01 13:41:00 +1100)
>
> ----------------------------------------------------------------
> ppc patch queue 2016-12-01
>
> Just a single migration / hotplug fix in this set. I believe it's
> important enough to go in this late in the 2.8 release process.
>
> ----------------------------------------------------------------
> Michael Roth (1):
> spapr: fix default DRC state for coldplugged LMBs
>
> hw/ppc/spapr.c | 5 +++++
> 1 file changed, 5 insertions(+)
Thanks, applied to my staging tree:
https://github.com/stefanha/qemu/commits/staging
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-12-01 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 4:44 [Qemu-devel] [PULL 0/1] ppc-for-2.8 queue 20161201 David Gibson
2016-12-01 4:44 ` [Qemu-devel] [PULL 1/1] spapr: fix default DRC state for coldplugged LMBs David Gibson
2016-12-01 13:39 ` Stefan Hajnoczi [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=20161201133934.GJ10441@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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).