From: David Hildenbrand <david@redhat.com>
To: Collin Walling <walling@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: thuth@redhat.com, wangyanan55@huawei.com, philmd@linaro.org,
marcel.apfelbaum@gmail.com, eduardo@habkost.net,
armbru@redhat.com
Subject: Re: [PATCH v1] target/s390x: move @deprecated-props to CpuModelExpansion Info
Date: Fri, 26 Jul 2024 23:16:11 +0200 [thread overview]
Message-ID: <7744345c-964a-445d-96e3-64f71183bfba@redhat.com> (raw)
In-Reply-To: <20240726203646.20279-1-walling@linux.ibm.com>
On 26.07.24 22:36, Collin Walling wrote:
> The @deprecated-props array did not make any sense to be a member of the
> CpuModelInfo struct, since this field would only be populated by a
> query-cpu-model-expansion response and ignored otherwise. Move this
> field to the CpuModelExpansionInfo struct where is makes more sense.
>
> References:
> - https://lists.gnu.org/archive/html/qemu-devel/2024-07/msg05996.html
> - commit eed0e8ffa38f0695c0519508f6e4f5a3297cbd67
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> ---
>
> @David, the previous commit header did not align with the changes made
> here, so I tagged this as a "v1" but added the previous conversation as
> a reference. I hope this is appropriate?
Thanks, I modified the "References" section and converted it to a "Fixes:".
It's now:
target/s390x: move @deprecated-props to CpuModelExpansion Info
The @deprecated-props array did not make any sense to be a member of the
CpuModelInfo struct, since this field would only be populated by a
query-cpu-model-expansion response and ignored otherwise. Move this
field to the CpuModelExpansionInfo struct where is makes more sense.
This was identified late during review [1] and we have to fix it up
while it's not part of an official QEMU release yet.
[1] https://lore.kernel.org/qemu-devel/20240719181741.35146-1-walling@linux.ibm.com/
Message-ID: <20240726203646.20279-1-walling@linux.ibm.com>
Fixes: eed0e8ffa38f ("target/s390x: filter deprecated properties based on model expansion type")
Signed-off-by: Collin Walling <walling@linux.ibm.com>
[ david: add "Fixes", explain why fix is required now and reference to v3 ]
Signed-off-by: David Hildenbrand <david@redhat.com>
Can you take a quick peek at
https://github.com/davidhildenbrand/qemu/tree/s390x-next
if everything is alright?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-07-26 21:17 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 [this message]
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
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=7744345c-964a-445d-96e3-64f71183bfba@redhat.com \
--to=david@redhat.com \
--cc=armbru@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 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).