From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [GIT PULL for qemu-pseries] pseries: Update SLOF firmware image
Date: Tue, 22 Oct 2019 10:49:58 +0200 [thread overview]
Message-ID: <1c3c1b36-a355-9ebb-9c68-8ae1af268fff@redhat.com> (raw)
In-Reply-To: <20191022040945.35730-1-aik@ozlabs.ru>
Hi Alekey,
On 10/22/19 6:09 AM, Alexey Kardashevskiy wrote:
> The following changes since commit 7cff77c24d8f5e558cef3538a44044d66aa225a5:
>
> spapr: Move SpaprIrq::nr_xirqs to SpaprMachineClass (2019-10-16 12:01:41 +1100)
>
> are available in the Git repository at:
>
> git@github.com:aik/qemu.git tags/qemu-slof-20191022
>
> for you to fetch changes up to 8e59d05f71ae783e12a8eb7eb582e0a86ba3d6dc:
>
> pseries: Update SLOF firmware image (2019-10-22 15:05:36 +1100)
>
> ----------------------------------------------------------------
> Alexey Kardashevskiy (1):
> pseries: Update SLOF firmware image
>
> pc-bios/README | 2 +-
> pc-bios/slof.bin | Bin 930640 -> 928552 bytes
> roms/SLOF | 2 +-
> 3 files changed, 2 insertions(+), 2 deletions(-)
Looking at commit 8e59d05f71ae which update the SLOF submodule,
in your future updates can you include the git shortlog in the
commit description?
Simply:
$ git shortlog qemu-slof-20190911..qemu-slof-20191022
Alexey Kardashevskiy (3):
pci: Align PCI node names with QEMU
libusb: Fix compiler warnings with gcc9
version: update to 20191022
Thomas Huth (1):
ipv6: Fix gcc9 warnings
Thanks,
Phil.
next prev parent reply other threads:[~2019-10-22 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 4:09 [GIT PULL for qemu-pseries] pseries: Update SLOF firmware image Alexey Kardashevskiy
2019-10-22 7:41 ` David Gibson
2019-10-22 8:49 ` Philippe Mathieu-Daudé [this message]
2019-10-23 0:04 ` Alexey Kardashevskiy
2019-10-23 1:07 ` Eric Blake
-- strict thread matches above, loose matches on Subject: below --
2019-12-06 1:25 Alexey Kardashevskiy
2019-12-06 1:38 ` David Gibson
2019-12-06 11:18 ` 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=1c3c1b36-a355-9ebb-9c68-8ae1af268fff@redhat.com \
--to=philmd@redhat.com \
--cc=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).