From: David Gibson <david@gibson.dropbear.id.au>
To: peter.maydell@linaro.org
Cc: agraf@suse.de, qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PULL 0/1] ppc-for-2.6 queue 20160423
Date: Sat, 23 Apr 2016 16:57:59 +1000 [thread overview]
Message-ID: <1461394680-12913-1-git-send-email-david@gibson.dropbear.id.au> (raw)
The following changes since commit 53343338a6e7b83777b82803398572b40afc8c0f:
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2016-04-22 16:17:12 +0100)
are available in the git repository at:
git://github.com/dgibson/qemu.git tags/ppc-for-2.6-20160423
for you to fetch changes up to da34fed707a3a3ffa229f4e724aea06da1b53fb0:
hw/ppc/spapr: Fix crash when specifying bad parameters to spapr-pci-host-bridge (2016-04-23 16:52:20 +1000)
----------------------------------------------------------------
ppc patch queue for 2016-03-23
A single fix for a bug in parameter handling for the spapr PCI host
bridge.
----------------------------------------------------------------
Peter,
This is definitely a bug fix, but it's not a regression since 2.5.
Your judgement call as to whether to merge it this late in the 2.6
cycle.
Thomas Huth (1):
hw/ppc/spapr: Fix crash when specifying bad parameters to spapr-pci-host-bridge
hw/ppc/spapr.c | 9 ++++-----
hw/ppc/spapr_pci.c | 3 +++
2 files changed, 7 insertions(+), 5 deletions(-)
next reply other threads:[~2016-04-23 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 6:57 David Gibson [this message]
2016-04-23 6:58 ` [Qemu-devel] [PULL 1/1] hw/ppc/spapr: Fix crash when specifying bad parameters to spapr-pci-host-bridge David Gibson
2016-04-25 10:47 ` [Qemu-devel] [PULL 0/1] ppc-for-2.6 queue 20160423 Peter Maydell
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=1461394680-12913-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--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).