From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Cc: "Michal Prívozník" <mprivozn@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/1] EDK2 firmware patches
Date: Wed, 7 Aug 2019 14:45:42 +0200 [thread overview]
Message-ID: <c4221994-f66d-8d51-ea9b-444b98857c70@redhat.com> (raw)
In-Reply-To: <9625d2b7-e61f-ead6-78ef-e2ca7b88b878@redhat.com>
On 08/05/19 16:29, Philippe Mathieu-Daudé wrote:
> On 8/5/19 4:14 PM, Peter Maydell wrote:
>> On Mon, 5 Aug 2019 at 15:11, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>>
>>> Hi Peter,
>>>
>>> On 8/5/19 3:13 PM, Michal Prívozník wrote:
>>>> On 8/3/19 12:22 PM, Peter Maydell wrote:
>>>>> On Sat, 3 Aug 2019 at 09:26, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>>>>>
>>>>>> The following changes since commit 9bcf2dfa163f67b0fec6ee0fe88ad5dc5d69dc59:
>>>>>>
>>>>>> Merge remote-tracking branch 'remotes/elmarco/tags/slirp-CVE-2019-14378-pull-request' into staging (2019-08-02 13:06:03 +0100)
>>>>>>
>>>>>> are available in the Git repository at:
>>>>>>
>>>>>> https://gitlab.com/philmd/qemu.git tags/edk2-next-20190803
>>>>>>
>>>>>> for you to fetch changes up to 177cd674d6203d3c1a98e170ea56c5a904ac4ce8:
>>>>>>
>>>>>> Makefile: remove DESTDIR from firmware file content (2019-08-03 09:52:32 +0200)
>>>>>>
>>>>>> ----------------------------------------------------------------
>>>>>> A harmless build-sys patch that fixes a regression affecting Linux
>>>>>> distributions packaging QEMU.
>>>>>>
>>>>>> ----------------------------------------------------------------
>>>>>>
>>>>>> Olaf Hering (1):
>>>>>> Makefile: remove DESTDIR from firmware file content
>>>>>
>>>>> Is this pullreq intended for 4.1 ?
>>>
>>> Sorry, I was not sure how to comment on the pullreq cover (everything
>>> between the '---' lines get include in the merge commit description).
>>
>> Depends on your workflow. For me my pull-request-creation
>> script creates a bunch of files which will be the emails
>> to be sent out, and I can manually edit the 'cover letter'
>> email before sending everything.
>
> OK (I don't want to give you extra manual work).
>
>>> This fix a regression introduced during the current development cycle.
>>> Already 3 different distributions hit this issue and complained (Suse,
>>> ArchLinux and Fedora).
>>> This is not a critical/security issue and distributions can easily
>>> backport this patch, but since there is a RC4 planned, it would be nice
>>> regarding distributors to fix this if possible.
>>
>> OK, sounds good -- I just wanted to check. I've pushed the
>> pullreq to master.
>
> Thank you!
>
Thank you all, I've updated <https://bugs.launchpad.net/qemu/+bug/1838703>.
Laszlo
prev parent reply other threads:[~2019-08-07 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 8:25 [Qemu-devel] [PULL 0/1] EDK2 firmware patches Philippe Mathieu-Daudé
2019-08-03 8:25 ` [Qemu-devel] [PULL 1/1] Makefile: remove DESTDIR from firmware file content Philippe Mathieu-Daudé
2019-08-03 10:22 ` [Qemu-devel] [PULL 0/1] EDK2 firmware patches Peter Maydell
2019-08-05 13:13 ` Michal Prívozník
2019-08-05 14:11 ` Philippe Mathieu-Daudé
2019-08-05 14:14 ` Peter Maydell
2019-08-05 14:29 ` Philippe Mathieu-Daudé
2019-08-07 12:45 ` Laszlo Ersek [this message]
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=c4221994-f66d-8d51-ea9b-444b98857c70@redhat.com \
--to=lersek@redhat.com \
--cc=mprivozn@redhat.com \
--cc=peter.maydell@linaro.org \
--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).