From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
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 20191206
Date: Fri, 6 Dec 2019 21:29:03 +1100 [thread overview]
Message-ID: <20191206102903.GM5031@umbus.fritz.box> (raw)
In-Reply-To: <CAFEAcA-oGLx+mcgqxC6-QRv9dSdzOqvM8g7q7SzUuAqKSZU-tA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
On Fri, Dec 06, 2019 at 09:52:54AM +0000, Peter Maydell wrote:
> On Fri, 6 Dec 2019 at 04:41, David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > The following changes since commit 1bdc319ab5d289ce6b822e06fb2b13666fd9278e:
> >
> > Update version for v4.2.0-rc4 release (2019-12-03 17:56:30 +0000)
> >
> > are available in the Git repository at:
> >
> > git://github.com/dgibson/qemu.git tags/ppc-for-4.2-20191206
> >
> > for you to fetch changes up to d887a8cfc083bcf3856f9f42352989f3624e0cae:
> >
> > pseries: Update SLOF firmware image (2019-12-06 15:33:23 +1100)
> >
> > ----------------------------------------------------------------
> > ppc patch queue 2019-12-06
> >
> > This is a last minute pull request for ppc-for-4.2. I know it's very
> > late in freeze, but this does fix 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.
>
> I really really really don't want to do an rc5. This would
> have to be "everybody using ppc gets crashes" for me to
> really want to put it in at this point...
Yeah, alright. I'll send it to Mike for a 4.2.1.
--
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 --]
next prev parent reply other threads:[~2019-12-06 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 4:41 [PULL 0/1] ppc-for-4.2 queue 20191206 David Gibson
2019-12-06 4:41 ` [PULL 1/1] pseries: Update SLOF firmware image David Gibson
2019-12-06 9:52 ` [PULL 0/1] ppc-for-4.2 queue 20191206 Peter Maydell
2019-12-06 10:29 ` David Gibson [this message]
2019-12-06 11:19 ` Peter Maydell
2019-12-06 13:40 ` Peter Maydell
2019-12-09 7:00 ` David Gibson
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=20191206102903.GM5031@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=groug@kaod.org \
--cc=lvivier@redhat.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).