From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-s390x@nongnu.org,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>
Cc: qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: Re: [PATCH 0/8] s390x: Remove deprecated machine types v2.9 up to v2.12
Date: Wed, 15 Jan 2025 18:04:12 +0100 [thread overview]
Message-ID: <1ee72a8e-5e06-482f-8dea-9575de1da8af@redhat.com> (raw)
In-Reply-To: <a20b0629-78ba-4ae6-981c-bbc1fbf0a866@linaro.org>
On 15/01/2025 17.35, Philippe Mathieu-Daudé wrote:
> On 15/1/25 08:38, Thomas Huth wrote:
>> These machine types have been marked as deprecated two releases ago,
>> and are older than 6 years, so according to our support policy, it
>> should be fine to remove them now.
>>
>> Thomas Huth (8):
>> hw/s390x/s390-virtio-ccw: Remove the deprecated 2.9 machine type
>> hw/s390x/s390-virtio-ccw: Remove the deprecated 2.10 and 2.11 machine
>> types
>> target/s390x/gen-features: Remove the v2.11 qemu CPU model
>> hw/s390x/s390-virtio-ccw: Remove the deprecated 2.12 machine type
>
> Should this be documented in docs/about/removed-features.rst?
We've got a generic paragraph about machine removal now:
https://gitlab.com/qemu-project/qemu/-/commit/ce80c4fa6ff
So I think we don't should manually mention each and every removed versioned
machine type in removed-features.rst anymore. But some generic sentence in
removed-features.rst about this would be good, too. I'll prepare a patch for it.
Thomas
prev parent reply other threads:[~2025-01-15 17:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 7:38 [PATCH 0/8] s390x: Remove deprecated machine types v2.9 up to v2.12 Thomas Huth
2025-01-15 7:38 ` [PATCH 1/8] hw/s390x/s390-virtio-ccw: Remove the deprecated 2.9 machine type Thomas Huth
2025-01-15 7:38 ` [PATCH 2/8] hw/s390x/css: Remove the obsolete "css_migration_enabled" variable Thomas Huth
2025-01-15 8:54 ` Philippe Mathieu-Daudé
2025-01-15 7:38 ` [PATCH 3/8] hw/s390x/s390-stattrib: Remove the old migration_enabled flag Thomas Huth
2025-01-15 8:59 ` Philippe Mathieu-Daudé
2025-01-15 7:38 ` [PATCH 4/8] hw/intc/s390_flic: Remove the obsolete " Thomas Huth
2025-01-15 9:01 ` Philippe Mathieu-Daudé
2025-01-15 7:38 ` [PATCH 5/8] hw/s390x/s390-virtio-ccw: Remove the deprecated 2.10 and 2.11 machine types Thomas Huth
2025-05-01 22:42 ` Philippe Mathieu-Daudé
2025-01-15 7:38 ` [PATCH 6/8] hw/s390x/event-facility: Remove the obsolete "allow_all_mask_sizes" code Thomas Huth
2025-01-15 9:03 ` Philippe Mathieu-Daudé
2025-01-15 7:38 ` [PATCH 7/8] target/s390x/gen-features: Remove the v2.11 qemu CPU model Thomas Huth
2025-04-23 7:54 ` Thomas Huth
2025-01-15 7:38 ` [PATCH 8/8] hw/s390x/s390-virtio-ccw: Remove the deprecated 2.12 machine type Thomas Huth
2025-05-01 22:43 ` Philippe Mathieu-Daudé
2025-01-15 16:35 ` [PATCH 0/8] s390x: Remove deprecated machine types v2.9 up to v2.12 Philippe Mathieu-Daudé
2025-01-15 17:04 ` Thomas Huth [this message]
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=1ee72a8e-5e06-482f-8dea-9575de1da8af@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).