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>,
linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: zfcp changes for v6.3
Date: Tue, 21 Feb 2023 20:46:17 -0500 [thread overview]
Message-ID: <yq1cz62pj7t.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <cover.1677000450.git.bblock@linux.ibm.com> (Benjamin Block's message of "Tue, 21 Feb 2023 18:55:57 +0100")
Benjamin,
> here is a small set of changes for the zFCP device driver. These are
> basically follow-up changes I made after the fix I send in
> <979f6e6019d15f91ba56182f1aaf68d61bf37fc6.1668595505.git.bblock@linux.ibm.com>
> that refactor some related areas in the driver, and add some
> additional tracing if we ever should run into a similar situation
> somehow.
>
> It would be nice, if you could still include them for v6.3. Not sure if
> I'm too late already.
It's a bit late. I merged them to 6.3/scsi-staging for now but may defer
to 6.4 depending on how busy the various code checking robots are.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-02-22 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 17:55 zfcp changes for v6.3 Benjamin Block
2023-02-21 17:55 ` [PATCH 1/3] zfcp: make the type for accessing request hashtable buckets size_t Benjamin Block
2023-02-21 17:55 ` [PATCH 2/3] zfcp: change the type of all fsf request id fields and variables to u64 Benjamin Block
2023-02-21 17:56 ` [PATCH 3/3] zfcp: trace when request remove fails after qdio send fails Benjamin Block
2023-02-22 1:46 ` Martin K. Petersen [this message]
2023-02-22 9:50 ` zfcp changes for v6.3 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=yq1cz62pj7t.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox