From: "Cédric Le Goater" <clg@redhat.com>
To: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: "Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"David Hildenbrand" <david@redhat.com>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Thomas Huth" <thuth@redhat.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: [PATCH 0/3] s390x: Simplify SCLPDevice usage
Date: Thu, 2 May 2024 15:15:30 +0200 [thread overview]
Message-ID: <20240502131533.377719-1-clg@redhat.com> (raw)
Hello,
Here is a little series reworking the SCLPDevice initialization in the
machine to simplify its use.
Applies on top of :
https://lore.kernel.org/qemu-devel/20240430190843.453903-1-thuth@redhat.com/
Thanks,
C.
Cédric Le Goater (3):
s390x: Introduce a SCLPDevice pointer under the machine
s390x/event-facility: Simplify sclp_get_event_facility_bus()
s390x/sclp: Simplify get_sclp_device()
include/hw/s390x/event-facility.h | 2 +-
include/hw/s390x/s390-virtio-ccw.h | 3 +++
include/hw/s390x/sclp.h | 2 --
hw/s390x/event-facility.c | 13 ++-----------
hw/s390x/s390-virtio-ccw.c | 18 ++++++++++++------
hw/s390x/sclp.c | 15 +++------------
6 files changed, 21 insertions(+), 32 deletions(-)
--
2.44.0
next reply other threads:[~2024-05-02 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 13:15 Cédric Le Goater [this message]
2024-05-02 13:15 ` [PATCH 1/3] s390x: Introduce a SCLPDevice pointer under the machine Cédric Le Goater
2024-05-02 17:04 ` Thomas Huth
2024-05-02 13:15 ` [PATCH 2/3] s390x/event-facility: Simplify sclp_get_event_facility_bus() Cédric Le Goater
2024-05-02 17:11 ` Thomas Huth
2024-05-02 13:15 ` [PATCH 3/3] s390x/sclp: Simplify get_sclp_device() Cédric Le Goater
2024-05-02 17:11 ` 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=20240502131533.377719-1-clg@redhat.com \
--to=clg@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=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).