From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
qemu-ppc <qemu-ppc@nongnu.org>, "Greg Kurz" <groug@kaod.org>,
"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [PULL 0/3] ppc-for-5.0 queue 20200417
Date: Fri, 17 Apr 2020 19:14:31 +1000 [thread overview]
Message-ID: <20200417091431.GC2102@umbus.fritz.box> (raw)
In-Reply-To: <CAFEAcA8qLznGS2YCFxz7QYrhbociZsqzEcxQPdp1rUy4OnnnFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
On Fri, Apr 17, 2020 at 09:28:46AM +0100, Peter Maydell wrote:
> On Fri, 17 Apr 2020 at 06:05, David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > The following changes since commit 20038cd7a8412feeb49c01f6ede89e36c8995472:
> >
> > Update version for v5.0.0-rc3 release (2020-04-15 20:51:54 +0100)
> >
> > are available in the Git repository at:
> >
> > git://github.com/dgibson/qemu.git tags/ppc-for-5.0-20200417
> >
> > for you to fetch changes up to 5ed195065cc6895f61b9d59bfa0a0536ed5ed51e:
> >
> > target/ppc: Fix mtmsr(d) L=1 variant that loses interrupts (2020-04-17 10:39:03 +1000)
> >
> > ----------------------------------------------------------------
> > ppc patch queue for 2020-04-17
> >
> > Here are a few late bugfixes for qemu-5.0 in the ppc target code.
> > Unless some really nasty last minute bug shows up, I expect this to be
> > the last ppc pull request for qemu-5.0.
> >
>
> We're past rc3 now, so I don't really want to do an rc4 unless we
> absolutely critically need to. How important are these bug fixes?
Eh, probably not important enough. They're not regressions AFAICT -
two fairly longstanding bugs, and one bug in a new feature. It can
wait until 5.1.
But, I guess throw them in if something else does force an rc4.
--
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:[~2020-04-17 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 5:05 [PULL 0/3] ppc-for-5.0 queue 20200417 David Gibson
2020-04-17 5:05 ` [PULL 1/3] linux-user/ppc: Fix padding in mcontext_t for ppc64 David Gibson
2020-04-17 5:05 ` [PULL 2/3] target/ppc: Fix wrong interpretation of the disposition flag David Gibson
2020-04-17 5:05 ` [PULL 3/3] target/ppc: Fix mtmsr(d) L=1 variant that loses interrupts David Gibson
2020-04-17 8:28 ` [PULL 0/3] ppc-for-5.0 queue 20200417 Peter Maydell
2020-04-17 9:14 ` David Gibson [this message]
2020-04-17 9:18 ` David Gibson
2020-04-17 9:21 ` Peter Maydell
2020-04-17 9:22 ` David Gibson
2020-04-20 21:19 ` 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=20200417091431.GC2102@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--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).