From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Eric Farman <farman@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
qemu-s390x@nongnu.org, Eduardo Habkost <eduardo@habkost.net>,
Yanan Wang <wangyanan55@huawei.com>,
Zhao Liu <zhao1.liu@intel.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v2 2/3] hw/s390x/ccw: Remove SCLPDevice::increment_size field
Date: Mon, 20 Oct 2025 12:23:44 +0200 [thread overview]
Message-ID: <93dc7be6-cee8-430b-b5b5-96bff9a0b8cc@redhat.com> (raw)
In-Reply-To: <20251020094903.72182-3-philmd@linaro.org>
On 20/10/2025 11.49, Philippe Mathieu-Daudé wrote:
> The SCLPDevice::increment_size field was only used by the
> s390-ccw-virtio-4.2 machine, which got removed. Remove it
> as now unused, along with the sclp_memory_init() method.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/hw/s390x/sclp.h | 5 +----
> hw/s390x/sclp.c | 34 +++-------------------------------
> 2 files changed, 4 insertions(+), 35 deletions(-)
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2025-10-20 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 9:48 [PATCH v2 0/3] hw/s390x: Remove s390-ccw-virtio-4.2 machine Philippe Mathieu-Daudé
2025-10-20 9:49 ` [PATCH v2 1/3] hw/s390x/ccw: Remove deprecated " Philippe Mathieu-Daudé
2025-10-20 10:20 ` Thomas Huth
2025-10-20 9:49 ` [PATCH v2 2/3] hw/s390x/ccw: Remove SCLPDevice::increment_size field Philippe Mathieu-Daudé
2025-10-20 10:23 ` Thomas Huth [this message]
2025-10-20 9:49 ` [PATCH v2 3/3] hw/core/machine: Remove MachineClass::fixup_ram_size callback Philippe Mathieu-Daudé
2025-10-20 10:24 ` Thomas Huth
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=93dc7be6-cee8-430b-b5b5-96bff9a0b8cc@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mjrosato@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 \
--cc=wangyanan55@huawei.com \
--cc=zhao1.liu@intel.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).