qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PULL v2 0/2] Block patches


From: Peter Maydell
Subject: Re: [PULL v2 0/2] Block patches
Date: Fri, 3 Jul 2020 16:58:15 +0100

On Fri, 3 Jul 2020 at 12:14, Max Reitz <mreitz@redhat.com> wrote:
>
> On 03.07.20 12:47, Peter Maydell wrote:
> > On Fri, 3 Jul 2020 at 10:52, Max Reitz <mreitz@redhat.com> wrote:
> >>
> >> On 24.06.20 10:13, Max Reitz wrote:
> >>> The following changes since commit 
> >>> d88d5a3806d78dcfca648c62dae9d88d3e803bd2:
> >>>
> >>>   Merge remote-tracking branch 
> >>> 'remotes/philmd-gitlab/tags/renesas-hw-20200622' into staging (2020-06-23 
> >>> 13:55:52 +0100)
> >>>
> >>> are available in the Git repository at:
> >>>
> >>>   https://github.com/XanClic/qemu.git tags/pull-block-2020-06-24
> >>>
> >>> for you to fetch changes up to 24b861c0386a17ea31eb824310c21118fb7be883:
> >>>
> >>>   iotests: don't test qcow2.py inside 291 (2020-06-24 10:00:04 +0200)
> >>>
> >>> ----------------------------------------------------------------
> >>> Block patches:
> >>> - Two iotest fixes
> >>>
> >>> ----------------------------------------------------------------
> >>> This is v2, where I dropped Maxim’s LUKS keyslot amendment series and my
> >>> iotest patches, because both caused iotest failures on some test
> >>> machines.
> >>
> >> Ping?
> >>
> >> Or should I just send another pull request that includes Maxim’s
> >> original series to supersede this one altogether?
> >
> > Sorry, your resend just fell out of my to-process queue for some
> > reason; I can put it back in the list to process.
>
> That’d be great, thanks!


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/5.1
for any user-visible changes.

-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]