From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [GIT PULL for qemu-pseries] pseries: Update SLOF firmware image
Date: Tue, 10 Jul 2018 17:14:53 +1000 [thread overview]
Message-ID: <20180710171453.6e3eee34@aik.ozlabs.ibm.com> (raw)
In-Reply-To: <20180710064248.GM22363@umbus.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
On Tue, 10 Jul 2018 16:42:48 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Tue, Jul 10, 2018 at 12:22:44PM +1000, Alexey Kardashevskiy wrote:
> > On Mon, 2 Jul 2018 16:26:44 +1000
> > Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> >
> > > The following changes since commit edb1fb337f65f82fe32b989c4f018efe85c1dddb:
> > >
> > > pseries: Update SLOF firmware image (2018-07-02 16:21:30 +1000)
> > >
> > > are available in the git repository at:
> > >
> > > git@github.com:aik/qemu.git tags/qemu-slof-20180702
> > >
> > > for you to fetch changes up to edb1fb337f65f82fe32b989c4f018efe85c1dddb:
> > >
> > > pseries: Update SLOF firmware image (2018-07-02 16:21:30 +1000)
> > >
> > > ----------------------------------------------------------------
> > >
> > > I just missed a couple of gcc 8.1 fixes and thought I can still squeeze
> > > them before the 3.0 soft freeze.
> > >
> > >
> > > *** Note: this is not for master, this is for pseries
> >
> >
> > Not good for 3.1 either?
>
> Ugh.. somehow I missed this SLOF update request, and now we're in 3.0
> hard freeze.
>
> How bad are the bugs this SLOF update fixes?
These only fix gcc 8.1 warnings and runtime errors => not really
bugfixes so it is not a big deal if they miss 3.0.
--
Alexey
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-10 7:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 6:26 [Qemu-devel] [GIT PULL for qemu-pseries] pseries: Update SLOF firmware image Alexey Kardashevskiy
2018-07-10 2:22 ` Alexey Kardashevskiy
2018-07-10 6:42 ` David Gibson
2018-07-10 7:14 ` Alexey Kardashevskiy [this message]
2018-07-11 6:26 ` David Gibson
2018-07-11 10:53 ` Alexey Kardashevskiy
2018-07-12 1:01 ` David Gibson
2018-07-12 5:01 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2018-07-12 5:14 ` Alexey Kardashevskiy
2018-07-12 5:22 ` Thomas Huth
-- strict thread matches above, loose matches on Subject: below --
2019-09-12 1:36 [Qemu-devel] " Alexey Kardashevskiy
2019-09-19 0:13 ` Alexey Kardashevskiy
2019-07-19 1:53 Alexey Kardashevskiy
2019-07-03 2:39 Alexey Kardashevskiy
2019-07-03 3:05 ` David Gibson
2019-01-14 8:14 Alexey Kardashevskiy
2019-01-20 21:57 ` David Gibson
2018-07-02 7:22 Alexey Kardashevskiy
2017-07-24 5:35 Alexey Kardashevskiy
2017-07-24 10:51 ` David Gibson
2017-03-03 3:24 Alexey Kardashevskiy
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=20180710171453.6e3eee34@aik.ozlabs.ibm.com \
--to=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--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).