From: James Smart <jsmart2021@gmail.com>
To: Hannes Reinecke <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/5] lpfc: fixes for SCSI EH rework
Date: Thu, 19 Aug 2021 09:29:50 -0700 [thread overview]
Message-ID: <996b714d-e316-33ff-706b-7bac162587e8@gmail.com> (raw)
In-Reply-To: <20210818090827.134342-1-hare@suse.de>
On 8/18/2021 2:08 AM, Hannes Reinecke wrote:
> Hi all,
>
> with the SCSI EH rework the scsi_cmnd argument for the SCSI EH callbacks
> is going away, so we need to fixup the drivers to work without it.
>
> This patchset modifies the lpfc driver to not rely on a specific command
> for the EH callbacks.
>
> As usual, comments and reviews are welcome.
>
>
> Hannes Reinecke (5):
> lpfc: kill lpfc_bus_reset_handler
> lpfc: drop lpfc_no_handler()
> lpfc: use fc_block_rport()
> lpfc: use rport as argument for lpfc_send_taskmgmt()
> lpfc: use rport as argument for lpfc_chk_tgt_mapped()
>
> drivers/scsi/lpfc/lpfc_scsi.c | 138 +++++-----------------------------
> 1 file changed, 20 insertions(+), 118 deletions(-)
>
I think I've acked all of these in their prior posting
Reviewed-by: James Smart <jsmart2021@gmail.com>
-- james
prev parent reply other threads:[~2021-08-19 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 9:08 [PATCH 0/5] lpfc: fixes for SCSI EH rework Hannes Reinecke
2021-08-18 9:08 ` [PATCH 1/5] lpfc: kill lpfc_bus_reset_handler Hannes Reinecke
2021-08-18 9:08 ` [PATCH 2/5] lpfc: drop lpfc_no_handler() Hannes Reinecke
2021-08-18 9:08 ` [PATCH 3/5] lpfc: use fc_block_rport() Hannes Reinecke
2021-08-18 9:08 ` [PATCH 4/5] lpfc: use rport as argument for lpfc_send_taskmgmt() Hannes Reinecke
2021-08-18 9:08 ` [PATCH 5/5] lpfc: use rport as argument for lpfc_chk_tgt_mapped() Hannes Reinecke
2021-08-19 23:19 ` Julian Calaby
2021-08-19 16:29 ` James Smart [this message]
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=996b714d-e316-33ff-706b-7bac162587e8@gmail.com \
--to=jsmart2021@gmail.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--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 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.