qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Laurent Vivier <lvivier@redhat.com>,
	qemu-ppc <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Greg Kurz <groug@kaod.org>
Subject: Re: [PULL 0/1] ppc-for-4.2 queue 2019-12-06
Date: Mon, 9 Dec 2019 13:18:53 +0000	[thread overview]
Message-ID: <CAFEAcA93RzcW+JdhraP+-8h=RamLp6_UDN+hYvBgP0g_rvB0Tg@mail.gmail.com> (raw)
In-Reply-To: <20191209065928.204264-1-david@gibson.dropbear.id.au>

On Mon, 9 Dec 2019 at 06:59, David Gibson <david@gibson.dropbear.id.au> wrote:
>
> The following changes since commit 02f9c885edefae66d787847758d13ed60c0f539e:
>
>   Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2019-12-06 15:05:20 +0000)
>
> are available in the Git repository at:
>
>   git://github.com/dgibson/qemu.git tags/ppc-for-4.2-20191209
>
> for you to fetch changes up to a2fad86497b981426dc720236c15f2a99ca674a9:
>
>   pseries: Update SLOF firmware image (2019-12-09 12:16:26 +1100)
>
> ----------------------------------------------------------------
> ppc patch queue 2019-12-09
>
> This is a last minute pull request for ppc-for-4.2.  It fixes a
> regression: a bad interaction between the new qemu and SLOF device
> tree construction code means that SLOF will crash if PCI to PCI
> bridges are included in the system.
>
> This PR supersedes ppc-for-4.2-20191206.  This one has only a more
> minimal change to the firmware addressed only at fixing this bug and
> not incorporating some other unrelated changes that happened in the
> meantime.
>
> This is very late, maybe too late.  However, since there appears to be
> an -rc5 in the works for other reasons, I figured it was worth
> submitting this in case.
> ----------------------------------------------------------------


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
for any user-visible changes.

-- PMM


      parent reply	other threads:[~2019-12-09 13:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09  6:59 [PULL 0/1] ppc-for-4.2 queue 2019-12-06 David Gibson
2019-12-09  6:59 ` [PULL 1/1] pseries: Update SLOF firmware image David Gibson
2019-12-09 13:18 ` Peter Maydell [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='CAFEAcA93RzcW+JdhraP+-8h=RamLp6_UDN+hYvBgP0g_rvB0Tg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=lvivier@redhat.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).