From: Hannes Reinecke <hare@suse.de>
To: Lee Duncan <leeman.duncan@gmail.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Chengfeng Ye <dg573847474@gmail.com>,
Satish Kharat <satishkh@cisco.com>,
Sesidhar Baddela <sebaddel@cisco.com>,
Karan Tilak Kumar <kartilak@cisco.com>,
Lee Duncan <lduncan@suse.com>
Subject: Re: [PATCH v3 2/2] fnic: move fnic_fnic_flush_tx() to a work queue
Date: Fri, 9 Feb 2024 11:19:48 +0100 [thread overview]
Message-ID: <a602e869-1fb9-40e4-8aba-728d13c22dcb@suse.de> (raw)
In-Reply-To: <ce5ffa5d0ff82c2b2e283b3b4bff23291d49b05c.1707343839.git.lduncan@suse.com>
On 2/7/24 23:20, Lee Duncan wrote:
> From: Lee Duncan <lduncan@suse.com>
>
> Rather than call 'fnic_flush_tx()' from interrupt context we should
> be moving it onto a work queue to avoid any locking issues.
>
> Fixes: 1a1975551943f681772720f639ff42fbaa746212
Same here, please use the correct fixes tag.
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> Signed-off-by: Lee Duncan <lduncan@suse.com>
> ---
> drivers/scsi/fnic/fnic.h | 3 ++-
> drivers/scsi/fnic/fnic_fcs.c | 5 +++--
> drivers/scsi/fnic/fnic_main.c | 1 +
> drivers/scsi/fnic/fnic_scsi.c | 4 ++--
> 4 files changed, 8 insertions(+), 5 deletions(-)
>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Ivo Totev, Andrew McDonald,
Werner Knoblich
prev parent reply other threads:[~2024-02-09 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1707343839.git.lduncan@suse.com>
[not found] ` <c578cdcd46b60470535c4c4a953e6a1feca0dffd.1707343839.git.lduncan@suse.com>
2024-02-09 10:19 ` [PATCH v3 1/2] Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock" Hannes Reinecke
[not found] ` <ce5ffa5d0ff82c2b2e283b3b4bff23291d49b05c.1707343839.git.lduncan@suse.com>
2024-02-09 10:19 ` Hannes Reinecke [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=a602e869-1fb9-40e4-8aba-728d13c22dcb@suse.de \
--to=hare@suse.de \
--cc=dg573847474@gmail.com \
--cc=kartilak@cisco.com \
--cc=lduncan@suse.com \
--cc=leeman.duncan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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
all inboxes | Powered by JetHome®