public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Block <bblock@linux.ibm.com>
To: "James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"Steffen Maier" <maier@linux.ibm.com>
Cc: Benjamin Block <bblock@linux.ibm.com>,
	"Fedor Loshakov" <loshakov@linux.ibm.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Jiang Jian" <jiangjian@cdjrlc.com>,
	linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH 0/2] zfcp changes for v5.20
Date: Wed,  6 Jul 2022 17:59:38 +0200	[thread overview]
Message-ID: <cover.1657122360.git.bblock@linux.ibm.com> (raw)

Hello James, Martin,

here is a (very) small set of changes for the zFCP device driver. The
change from Jiang Jian came in recently, and Julian's patch has been
laying around for quite a while now, so I didn't want to let them linger
any longer in anticipation of any bigger change that might come.

It would be nice, if you could include them for v5.20.

Jiang Jian (1):
  scsi: zfcp: drop unexpected word "the" in the comments

Julian Wiedmann (1):
  scsi: zfcp: declare zfcp_sdev_attrs as static

 drivers/s390/scsi/zfcp_diag.h  | 2 +-
 drivers/s390/scsi/zfcp_sysfs.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-07-06 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 15:59 Benjamin Block [this message]
2022-07-06 15:59 ` [PATCH 1/2] scsi: zfcp: declare zfcp_sdev_attrs as static Benjamin Block
2022-07-06 15:59 ` [PATCH 2/2] scsi: zfcp: drop unexpected word "the" in the comments Benjamin Block
2022-07-07 21:34 ` [PATCH 0/2] zfcp changes for v5.20 Martin K. Petersen
2022-07-08  9:05   ` Benjamin Block
2022-07-14  4:22 ` Martin K. Petersen

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.1657122360.git.bblock@linux.ibm.com \
    --to=bblock@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=jejb@linux.ibm.com \
    --cc=jiangjian@cdjrlc.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