From: Can Guo <can.guo@oss.qualcomm.com>
To: "Bean Huo" <beanhuo@iokpp.de>,
"Peter Wang (王信友)" <peter.wang@mediatek.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"mani@kernel.org" <mani@kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"quic_rdwivedi@quicinc.com" <quic_rdwivedi@quicinc.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>
Subject: Re: [PATCH v5 2/2] scsi: ufs: core: Add support for static TX Equalization settings
Date: Fri, 29 May 2026 18:21:11 +0800 [thread overview]
Message-ID: <089e3959-08c3-4ed2-b0a3-3772d0ed7268@oss.qualcomm.com> (raw)
In-Reply-To: <e79510e02e1025f9a5c3dff0208cf63b22054bdb.camel@iokpp.de>
On 5/29/2026 6:19 PM, Bean Huo wrote:
> On Fri, 2026-05-29 at 16:42 +0800, Can Guo wrote:
>>> if (!lpd)
>>> return;
>>>
>>> if (lpd > UFS_MAX_LANES) {
>>> ...
>>> }
>> OK, got it.
>>
>> Thanks,
>> Can Guo.
> With this and Peter's num_elems rename addressed in v6, please add:
>
> Reviewed-by: Bean Huo <beanhuo@micron.com>
Thanks sir.
Can Guo.
>
> Thanks,
> Bean
>
prev parent reply other threads:[~2026-05-29 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260529011421.462046-1-can.guo@oss.qualcomm.com>
2026-05-29 1:14 ` [PATCH v5 1/2] dt-bindings: ufs: Document static TX Equalization settings properties Can Guo
2026-05-29 7:45 ` Peter Wang (王信友)
2026-05-29 1:14 ` [PATCH v5 2/2] scsi: ufs: core: Add support for static TX Equalization settings Can Guo
2026-05-29 8:04 ` Peter Wang (王信友)
2026-05-29 8:12 ` Can Guo
2026-05-29 8:40 ` Peter Wang (王信友)
2026-05-29 8:42 ` Can Guo
2026-05-29 10:19 ` Bean Huo
2026-05-29 10:21 ` Can Guo [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=089e3959-08c3-4ed2-b0a3-3772d0ed7268@oss.qualcomm.com \
--to=can.guo@oss.qualcomm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rdwivedi@quicinc.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®