[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PULL 0/1] EDK2 firmware patches
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [Qemu-devel] [PULL 0/1] EDK2 firmware patches |
Date: |
Mon, 5 Aug 2019 16:29:44 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 |
On 8/5/19 4:14 PM, Peter Maydell wrote:
> On Mon, 5 Aug 2019 at 15:11, Philippe Mathieu-Daudé <address@hidden> 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é <address@hidden> 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!