From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Benjamin Block <bblock@linux.ibm.com>
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Steffen Maier" <maier@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: Re: [PATCH 0/2] zfcp changes for v5.20
Date: Thu, 07 Jul 2022 17:34:11 -0400 [thread overview]
Message-ID: <yq11quw620k.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <cover.1657122360.git.bblock@linux.ibm.com> (Benjamin Block's message of "Wed, 6 Jul 2022 17:59:38 +0200")
Benjamin,
> 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.
Applied to 5.20/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-07-07 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 15:59 [PATCH 0/2] zfcp changes for v5.20 Benjamin Block
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 ` Martin K. Petersen [this message]
2022-07-08 9:05 ` [PATCH 0/2] zfcp changes for v5.20 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=yq11quw620k.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=bblock@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 \
/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.