From: Markus Armbruster <armbru@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Collin Walling <walling@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org, thuth@redhat.com,
wangyanan55@huawei.com, philmd@linaro.org,
marcel.apfelbaum@gmail.com, eduardo@habkost.net
Subject: Re: [PATCH v1] target/s390x: move @deprecated-props to CpuModelExpansion Info
Date: Mon, 29 Jul 2024 16:36:16 +0200 [thread overview]
Message-ID: <87msm0b6zj.fsf@pond.sub.org> (raw)
In-Reply-To: <f42a8801-f49d-48b6-84a4-467c89e78657@redhat.com> (David Hildenbrand's message of "Mon, 29 Jul 2024 16:22:16 +0200")
David Hildenbrand <david@redhat.com> writes:
>>>> The simplest way to address 4 is to tack 'if': 'TARGET_S390X' to
>>>> @deprecated-props.
>>>>
>>>
>>> diff --git a/qapi/machine-target.json b/qapi/machine-target.json
>>> index 09dec2b9bb..0be95d559c 100644
>>> --- a/qapi/machine-target.json
>>> +++ b/qapi/machine-target.json
>>> @@ -253,7 +253,7 @@
>>> ##
>>> { 'struct': 'CpuModelExpansionInfo',
>>> 'data': { 'model': 'CpuModelInfo',
>>> - '*deprecated-props': ['str'] },
>>> + '*deprecated-props' : { 'type': ['str'], 'if': 'TARGET_S390X' } },
>>> 'if': { 'any': [ 'TARGET_S390X',
>>> 'TARGET_I386',
>>> 'TARGET_ARM',
>>>
>>>
>>> Should do the trick, right?
>>
>> Yes. Break the line before 'if', please.
>
> Ack
>
> [...]
>
>>
>> Questions?
>
> As clear as it can get, thanks! :)
>
> That would leave us with:
Looks good to me!
next prev parent reply other threads:[~2024-07-29 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 20:36 [PATCH v1] target/s390x: move @deprecated-props to CpuModelExpansion Info Collin Walling
2024-07-26 21:16 ` David Hildenbrand
2024-07-26 22:38 ` Collin Walling
2024-07-27 6:02 ` Markus Armbruster
2024-07-29 9:52 ` David Hildenbrand
2024-07-29 14:15 ` Markus Armbruster
2024-07-29 14:22 ` David Hildenbrand
2024-07-29 14:36 ` Markus Armbruster [this message]
2024-07-29 14:49 ` Collin Walling
2024-07-29 15:24 ` David Hildenbrand
2024-07-29 19:25 ` Collin Walling
2024-07-29 19:48 ` David Hildenbrand
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=87msm0b6zj.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.com \
--cc=wangyanan55@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.