qemu-devel
[Top][All Lists]
Advanced

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

Re: [PULL v2 00/28] QAPI patches patches for 2022-10-25


From: Markus Armbruster
Subject: Re: [PULL v2 00/28] QAPI patches patches for 2022-10-25
Date: Thu, 03 Nov 2022 15:02:03 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

Stefan Hajnoczi <stefanha@gmail.com> writes:

> On Wed, 26 Oct 2022 at 14:44, Markus Armbruster <armbru@redhat.com> wrote:
>>
>> The following changes since commit e750a7ace492f0b450653d4ad368a77d6f660fb8:
>>
>>   Merge tag 'pull-9p-20221024' of https://github.com/cschoenebeck/qemu into 
>> staging (2022-10-24 14:27:12 -0400)
>>
>> are available in the Git repository at:
>>
>>   https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2022-10-25-v2
>>
>> for you to fetch changes up to c0f24f8f31ca82e34ef037bfe34ef71eeecb401d:
>>
>>   qapi: Drop temporary logic to support conversion step by step (2022-10-26 
>> 20:08:52 +0200)
>>
>> ----------------------------------------------------------------
>> QAPI patches patches for 2022-10-25
>>
>> ----------------------------------------------------------------
>> Markus Armbruster (28):
>>       docs/devel/qapi-code-gen: Update example to match current code
>>       qapi: Tidy up whitespace in generated code
>>       docs/devel/qapi-code-gen: Extend example for next commit's change
>>       qapi: Start to elide redundant has_FOO in generated C
>>       qapi tests: Elide redundant has_FOO in generated C
>>       qapi acpi: Elide redundant has_FOO in generated C
>>       qapi audio: Elide redundant has_FOO in generated C
>>       qapi block: Elide redundant has_FOO in generated C
>
> This commit breaks qemu-iotests 056 in CI. I have included
> instructions for reproducing it locally below. I will drop this pull
> request for now. Please note that the QEMU 7.2 soft freeze is on
> Tuesday.

I finally managed to debug this one.  I think a v3 is best.  And then
we'll see whether the series can still go in, or needs to wait for the
next cycle.

Thanks!




reply via email to

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