From: Stefan Haberland <sth@linux.ibm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
Jan Hoeppner <hoeppner@linux.ibm.com>,
linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Miroslav Franc <mfranc@suse.cz>
Subject: [PATCH RESEND 00/11] s390/dasd: string handling cleanups
Date: Thu, 8 Feb 2024 17:42:39 +0100 [thread overview]
Message-ID: <20240208164248.540985-1-sth@linux.ibm.com> (raw)
Hi Jens,
looks like the patchset was not applied for the last merge window.
So I am resending it rebased to the current for-next branch.
Please apply the patches for the upcomming merge window.
They clean up the string handling in the DASD driver.
In addition there is a patch that fixes double module refcount decrement.
Jan Höppner (10):
s390/dasd: Simplify uid string generation
s390/dasd: Use sysfs_emit() over sprintf()
s390/dasd: Remove unnecessary errorstring generation
s390/dasd: Move allocation error message to DBF
s390/dasd: Remove unused message logging macros
s390/dasd: Use dev_err() over printk()
s390/dasd: Remove %p format specifier from error messages
s390/dasd: Remove PRINTK_HEADER and KMSG_COMPONENT definitions
s390/dasd: Use dev_*() for device log messages
s390/dasd: Improve ERP error messages
Miroslav Franc (1):
s390/dasd: fix double module refcount decrement
drivers/s390/block/dasd.c | 106 +++++++------------
drivers/s390/block/dasd_3990_erp.c | 80 ++++-----------
drivers/s390/block/dasd_alias.c | 8 --
drivers/s390/block/dasd_devmap.c | 34 +++----
drivers/s390/block/dasd_diag.c | 4 -
drivers/s390/block/dasd_eckd.c | 157 +++++++++++------------------
drivers/s390/block/dasd_eer.c | 7 --
drivers/s390/block/dasd_erp.c | 9 +-
drivers/s390/block/dasd_fba.c | 55 ++++------
drivers/s390/block/dasd_genhd.c | 5 -
drivers/s390/block/dasd_int.h | 29 ------
drivers/s390/block/dasd_ioctl.c | 6 --
drivers/s390/block/dasd_proc.c | 5 -
13 files changed, 154 insertions(+), 351 deletions(-)
--
2.40.1
next reply other threads:[~2024-02-08 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 16:42 Stefan Haberland [this message]
2024-02-08 16:42 ` [PATCH RESEND 01/11] s390/dasd: Simplify uid string generation Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 02/11] s390/dasd: Use sysfs_emit() over sprintf() Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 03/11] s390/dasd: Remove unnecessary errorstring generation Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 04/11] s390/dasd: Move allocation error message to DBF Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 05/11] s390/dasd: Remove unused message logging macros Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 06/11] s390/dasd: Use dev_err() over printk() Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 07/11] s390/dasd: Remove %p format specifier from error messages Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 08/11] s390/dasd: Remove PRINTK_HEADER and KMSG_COMPONENT definitions Stefan Haberland
2024-02-08 16:42 ` [PATCH RESEND 09/11] s390/dasd: Use dev_*() for device log messages Stefan Haberland
2024-02-08 17:12 ` [PATCH RESEND 00/11] s390/dasd: string handling cleanups Jens Axboe
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=20240208164248.540985-1-sth@linux.ibm.com \
--to=sth@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mfranc@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.