From: Heiko Carstens <hca@linux.ibm.com>
To: "Ricardo B. Marliere" <ricardo@marliere.net>
Cc: Vineeth Vijayan <vneethv@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] s390: struct bus_type cleanup
Date: Tue, 6 Feb 2024 09:31:02 +0100 [thread overview]
Message-ID: <20240206083102.11958-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20240203-bus_cleanup-s390-v1-0-ac891afc7282@marliere.net>
On Sat, Feb 03, 2024 at 11:57:57AM -0300, Ricardo B. Marliere wrote:
> This series is part of an effort to cleanup the users of the driver
> core, as can be seen in many recent patches authored by Greg across the
> tree (e.g. [1]). Specifically, this series is part of the task of
> splitting one of his TODOs [2].
>
> ---
> [1]: https://lore.kernel.org/lkml/?q=f%3Agregkh%40linuxfoundation.org+s%3A%22make%22+and+s%3A%22const%22
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/commit/?h=bus_cleanup&id=26105f537f0c60eacfeb430abd2e05d7ddcdd8aa
>
> Signed-off-by: Ricardo B. Marliere <ricardo@marliere.net>
>
> ---
> Ricardo B. Marliere (6):
> s390: ccwgroup: make ccwgroup_bus_type const
> s390: cio: make css_bus_type const
> s390: cio: make ccw_bus_type const
> s390: cio: make scm_bus_type const
> s390: AP: make ap_bus_type const
> s390: vfio-ap: make matrix_bus const
>
> drivers/s390/cio/ccwgroup.c | 4 ++--
> drivers/s390/cio/css.c | 4 ++--
> drivers/s390/cio/device.c | 4 ++--
> drivers/s390/cio/scm.c | 2 +-
> drivers/s390/crypto/ap_bus.c | 4 ++--
> drivers/s390/crypto/vfio_ap_drv.c | 2 +-
> 6 files changed, 10 insertions(+), 10 deletions(-)
Applied, thanks!
prev parent reply other threads:[~2024-02-06 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 14:57 [PATCH 0/6] s390: struct bus_type cleanup Ricardo B. Marliere
2024-02-03 14:57 ` [PATCH 1/6] s390: ccwgroup: make ccwgroup_bus_type const Ricardo B. Marliere
2024-02-03 14:57 ` [PATCH 2/6] s390: cio: make css_bus_type const Ricardo B. Marliere
2024-02-03 14:58 ` [PATCH 3/6] s390: cio: make ccw_bus_type const Ricardo B. Marliere
2024-02-03 14:58 ` [PATCH 4/6] s390: cio: make scm_bus_type const Ricardo B. Marliere
2024-02-03 14:58 ` [PATCH 5/6] s390: AP: make ap_bus_type const Ricardo B. Marliere
2024-02-05 10:36 ` Harald Freudenberger
2024-02-03 14:58 ` [PATCH 6/6] s390: vfio-ap: make matrix_bus const Ricardo B. Marliere
2024-02-05 14:00 ` Jason J. Herne
2024-02-05 15:23 ` Anthony Krowiak
2024-02-05 16:02 ` Halil Pasic
2024-02-03 15:20 ` [PATCH 0/6] s390: struct bus_type cleanup Greg Kroah-Hartman
2024-02-06 8:31 ` Heiko Carstens [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=20240206083102.11958-A-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jjherne@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=ricardo@marliere.net \
--cc=svens@linux.ibm.com \
--cc=vneethv@linux.ibm.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