From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Qianfeng Rong <rongqianfeng@vivo.com>
Cc: James Smart <james.smart@broadcom.com>,
Dick Kennedy <dick.kennedy@broadcom.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"open list:EMULEX/BROADCOM LPFC FC/FCOE SCSI DRIVER"
<linux-scsi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/6] scsi: lpfc: use min() to improve code
Date: Tue, 19 Aug 2025 22:25:59 -0400 [thread overview]
Message-ID: <yq1sehmvidv.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250815121609.384914-4-rongqianfeng@vivo.com> (Qianfeng Rong's message of "Fri, 15 Aug 2025 20:16:05 +0800")
Qianfeng,
> Use min_t() to reduce the code in lpfc_sli4_driver_resource_setup()
> and lpfc_nvme_prep_io_cmd(), and improve readability.
Applied to 6.18/scsi-staging, thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2025-08-20 2:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 12:16 [PATCH 0/6] scsi: use min()/min_t()/max() to improve code Qianfeng Rong
2025-08-15 12:16 ` [PATCH 1/6] scsi: bfa: use min_t() " Qianfeng Rong
2025-08-20 12:13 ` David Laight
2025-08-15 12:16 ` [PATCH 2/6] scsi: hpsa: use min()/min_t() " Qianfeng Rong
2025-08-15 19:59 ` Don.Brace
2025-08-20 2:25 ` Martin K. Petersen
2025-08-20 12:02 ` David Laight
2025-08-20 12:50 ` Qianfeng Rong
2025-08-20 17:57 ` David Laight
2025-08-15 12:16 ` [PATCH 3/6] scsi: lpfc: use min() " Qianfeng Rong
2025-08-15 19:55 ` Justin Tee
2025-08-20 2:25 ` Martin K. Petersen [this message]
2025-08-15 12:16 ` [PATCH 4/6] scsi: megaraid_sas: use max() " Qianfeng Rong
2025-08-15 12:16 ` [PATCH 5/6] scsi: mpi3mr: use min() " Qianfeng Rong
2025-08-15 12:16 ` [PATCH 6/6] scsi: qla2xxx: " Qianfeng Rong
2025-08-26 2:33 ` (subset) [PATCH 0/6] scsi: use min()/min_t()/max() " 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=yq1sehmvidv.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rongqianfeng@vivo.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