qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Prasad J Pandit <pjp@fedoraproject.org>,
	Cole Robinson <crobinso@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Bruce Rogers <brogers@suse.com>
Subject: Re: [PATCH-for-4.2? 0/1] roms/edk2: update submodule to edk2-stable201911, fixing low severity CVEs
Date: Fri, 29 Nov 2019 13:36:43 +0100	[thread overview]
Message-ID: <CAP+75-W4hi7oU636CN9f8d1aqrasxBYywwY7gvcVVSh36jnpOw@mail.gmail.com> (raw)
In-Reply-To: <9e052d2b-50c9-9370-a279-002987375f89@redhat.com>

On Fri, Nov 29, 2019 at 1:10 PM Laszlo Ersek <lersek@redhat.com> wrote:
>
> Hi Phil,
>
> On 11/29/19 11:44, Philippe Mathieu-Daudé wrote:
> > I had this commit ready for when the next EDK2 release were go out,
> > which just happened: https://edk2.groups.io/g/devel/message/51502
> >
> > Laszlo doesn't think it's worth the churn to rush to get this update
> > into into 4.2-rc4: https://bugs.launchpad.net/qemu/+bug/1852196/comments/2
> >
> > I agree with Laszlo, users shouldn't use the EDK2 bundled within QEMU
> > in production, and should rather build it from source. However some
> > distributions seem to rely on this convenience way to package EDK2,
> > and few CVEs are fixed in this new release. So it might be worthwhile
> > to get this into 4.2-rc4. Anyhow distributions don't use QEMU stable
> > tag directly and backport patches, so if there is no other rc4 patch,
> > we could skip this for after 4.2, as Laszlo originally planned.
> >
> > Philippe Mathieu-Daudé (1):
> >   roms/edk2: update submodule from edk2-stable201905 to
> >     edk2-stable201911
> >
> >  roms/edk2 | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
>
> if we want to do this, then the above diffstat is not enough.
>
> - please evaluate whether we should do something like 9153b9d7401f
> ("roms/Makefile.edk2: update input file list for
> "pc-bios/edk2-licenses.txt"", 2019-06-14)
>
> - we need to rebuild the binaries: 3583cb29f28f ("pc-bios: refresh edk2
> build artifacts for edk2-stable201905", 2019-06-14)
>
> - we should update the README file: 541617cad344 ("pc-bios: update the
> README file with edk2-stable201905 information", 2019-06-14)

Oops sorry for missing all these points, I'll do them.



  reply	other threads:[~2019-11-29 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 10:44 [PATCH-for-4.2? 0/1] roms/edk2: update submodule to edk2-stable201911, fixing low severity CVEs Philippe Mathieu-Daudé
2019-11-29 10:44 ` [PATCH-for-4.2? 1/1] roms/edk2: update submodule from edk2-stable201905 to edk2-stable201911 Philippe Mathieu-Daudé
2019-11-29 12:10 ` [PATCH-for-4.2? 0/1] roms/edk2: update submodule to edk2-stable201911, fixing low severity CVEs Laszlo Ersek
2019-11-29 12:36   ` Philippe Mathieu-Daudé [this message]
2019-12-06  5:19     ` Philippe Mathieu-Daudé

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=CAP+75-W4hi7oU636CN9f8d1aqrasxBYywwY7gvcVVSh36jnpOw@mail.gmail.com \
    --to=philmd@redhat.com \
    --cc=brogers@suse.com \
    --cc=crobinso@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pjp@fedoraproject.org \
    --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).