From: Benjamin Block <bblock@linux.ibm.com>
To: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Benjamin Block <bblock@linux.ibm.com>,
Steffen Maier <maier@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Fedor Loshakov <loshakov@linux.ibm.com>,
Julian Wiedmann <jwi@linux.ibm.com>,
linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH 0/2] zfcp: small changes for 5.10
Date: Thu, 10 Sep 2020 21:49:14 +0200 [thread overview]
Message-ID: <cover.1599765652.git.bblock@linux.ibm.com> (raw)
Hello Martin, James,
here are some small changes for zfcp I'd like to include in 5.10 if
possible. They apply cleanly on Martin's `scsi-queue`, and James' `misc`
branches.
Both patches make the driver a bit cleaner, and hopefully easier to
maintain.
Both have been in our CI for quite a while now, running every night. I
also gave them a separate regression run just now with I/O and
error-injects such as cable pulls and other external error sources. So I
am rather confident that they don't break anything for us - apart from
that they're straight forward code changes.
As always, feedback and further reviews are appreciated :-)
Julian Wiedmann (2):
zfcp: use list_first_entry_or_null() in zfcp_erp_thread()
zfcp: clarify access to erp_action in zfcp_fsf_req_complete()
drivers/s390/scsi/zfcp_erp.c | 8 +++-----
drivers/s390/scsi/zfcp_fsf.c | 10 ++++++++--
2 files changed, 11 insertions(+), 7 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-10 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 19:49 Benjamin Block [this message]
2020-09-10 19:49 ` [PATCH 1/2] zfcp: use list_first_entry_or_null() in zfcp_erp_thread() Benjamin Block
2020-09-10 19:49 ` [PATCH 2/2] zfcp: clarify access to erp_action in zfcp_fsf_req_complete() Benjamin Block
2020-09-15 22:03 ` [PATCH 0/2] zfcp: small changes for 5.10 Martin K. Petersen
2020-09-22 3:56 ` Martin K. Petersen
2020-09-22 10:05 ` Benjamin Block
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=cover.1599765652.git.bblock@linux.ibm.com \
--to=bblock@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loshakov@linux.ibm.com \
--cc=maier@linux.ibm.com \
--cc=martin.petersen@oracle.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).