From: Justin Tee <justintee8345@gmail.com>
To: "Yury Norov (NVIDIA)" <yury.norov@gmail.com>
Cc: James Smart <james.smart@broadcom.com>,
Justin Tee <justin.tee@broadcom.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: lpfc: rework lpfc_sli4_fcf_rr_next_index_get()
Date: Thu, 18 Sep 2025 16:24:30 -0700 [thread overview]
Message-ID: <CABPRKS9mmUCig30yz4DE1JgAkS+NejeZwr74rd80F5actbS6_Q@mail.gmail.com> (raw)
In-Reply-To: <20250917141806.661826-1-yury.norov@gmail.com>
Hi Yury,
> + if (phba->fcf.fcf_pri[next].fcf_rec.flag & LPFC_FCF_FLOGI_FAILED == 0) {
May we change this to?
if (!(phba->fcf.fcf_pri[next].fcf_rec.flag & LPFC_FCF_FLOGI_FAILED)) {
Thank you for noticing and implementing the rework.
Regards,
Justin Tee
prev parent reply other threads:[~2025-09-18 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 14:18 [PATCH] scsi: lpfc: rework lpfc_sli4_fcf_rr_next_index_get() Yury Norov (NVIDIA)
2025-09-18 23:24 ` Justin Tee [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=CABPRKS9mmUCig30yz4DE1JgAkS+NejeZwr74rd80F5actbS6_Q@mail.gmail.com \
--to=justintee8345@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=james.smart@broadcom.com \
--cc=justin.tee@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yury.norov@gmail.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;
as well as URLs for NNTP newsgroup(s).