qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu devel list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/6] update edk2 submodule & binaries to edk2-stable201905
Date: Thu, 13 Jun 2019 17:12:10 +0200	[thread overview]
Message-ID: <611d1efd-3052-c98d-e88a-294d07c822ab@redhat.com> (raw)
In-Reply-To: <20190606133110.13754-1-lersek@redhat.com>

On 06/06/19 15:31, Laszlo Ersek wrote:
> Launchpad: https://bugs.launchpad.net/qemu/+bug/1831477
> Repo:      https://github.com/lersek/qemu.git
> Branch:    edk2-stable201905-lp-1831477
> 
> edk2-stable201905 has been released today; let's update QEMU's
> submodule, and the binaries built thereof. This should be the edk2
> release that goes into QEMU 4.1.
> 
> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
> 
> Thanks
> Laszlo
> 
> Laszlo Ersek (6):
>   roms/Makefile.edk2: define edk2-stable201905 network feature test
>     macros
>   roms/edk2: update submodule from edk2-stable201903 to
>     edk2-stable201905
>   roms/Makefile.edk2: remove edk2-stable201903 network feature test
>     macros
>   roms/Makefile.edk2: update input file list for
>     "pc-bios/edk2-licenses.txt"
>   pc-bios: refresh edk2 build artifacts for edk2-stable201905
>   pc-bios: update the README file with edk2-stable201905 information
> 
>  pc-bios/README                         |  14 +-
>  pc-bios/edk2-aarch64-code.fd.bz2       | Bin 1177603 -> 1178070 bytes
>  pc-bios/edk2-arm-code.fd.bz2           | Bin 1173662 -> 1172752 bytes
>  pc-bios/edk2-i386-code.fd.bz2          | Bin 1688659 -> 1736199 bytes
>  pc-bios/edk2-i386-secure-code.fd.bz2   | Bin 1881979 -> 1943949 bytes
>  pc-bios/edk2-licenses.txt              | 752 ++++++++++++++++++--
>  pc-bios/edk2-x86_64-code.fd.bz2        | Bin 1669280 -> 1717094 bytes
>  pc-bios/edk2-x86_64-secure-code.fd.bz2 | Bin 1901210 -> 1958037 bytes
>  roms/Makefile.edk2                     |  22 +-
>  roms/edk2                              |   2 +-
>  10 files changed, 714 insertions(+), 76 deletions(-)
> 

Ping :)


  parent reply	other threads:[~2019-06-13 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 13:31 [Qemu-devel] [PATCH 0/6] update edk2 submodule & binaries to edk2-stable201905 Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 1/6] roms/Makefile.edk2: define edk2-stable201905 network feature test macros Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 2/6] roms/edk2: update submodule from edk2-stable201903 to edk2-stable201905 Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 3/6] roms/Makefile.edk2: remove edk2-stable201903 network feature test macros Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 4/6] roms/Makefile.edk2: update input file list for "pc-bios/edk2-licenses.txt" Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 5/6] pc-bios: refresh edk2 build artifacts for edk2-stable201905 Laszlo Ersek
2019-06-06 13:31 ` [Qemu-devel] [PATCH 6/6] pc-bios: update the README file with edk2-stable201905 information Laszlo Ersek
2019-06-13 15:12 ` Laszlo Ersek [this message]
2019-06-13 17:41   ` [Qemu-devel] [PATCH 0/6] update edk2 submodule & binaries to edk2-stable201905 Philippe Mathieu-Daudé
2019-06-14 19:43     ` Laszlo Ersek

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=611d1efd-3052-c98d-e88a-294d07c822ab@redhat.com \
    --to=lersek@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@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).