From: Bart Van Assche <bvanassche@acm.org>
To: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, mani@kernel.org,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V3 4/4] ufs: ufs-qcom: Add support for limiting HS gear and rate
Date: Tue, 26 Aug 2025 08:37:10 -0700 [thread overview]
Message-ID: <db0a8b86-b048-489b-9b23-6987f48e9419@acm.org> (raw)
In-Reply-To: <20250826150855.7725-5-quic_rdwivedi@quicinc.com>
On 8/26/25 8:08 AM, Ram Kumar Dwivedi wrote:
> + if (host_params->hs_tx_gear != hs_gear_old) {
> + host->phy_gear = host_params->hs_tx_gear;
> + }
The recommended style in Linux kernel code is not to surround single
statements with braces.
Thanks,
Bart.
next prev parent reply other threads:[~2025-08-26 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 15:08 [PATCH V3 0/4] Add DT-based gear and rate limiting support Ram Kumar Dwivedi
2025-08-26 15:08 ` [PATCH V3 1/4] ufs: dt-bindings: Document gear and rate limit properties Ram Kumar Dwivedi
2025-08-26 15:35 ` Bart Van Assche
2025-08-28 16:25 ` Ram Kumar Dwivedi
2025-08-28 17:41 ` Krzysztof Kozlowski
2025-08-28 16:45 ` Ram Kumar Dwivedi
2025-08-28 17:22 ` Bart Van Assche
2025-09-01 4:07 ` Manivannan Sadhasivam
2025-09-01 16:01 ` Ram Kumar Dwivedi
2025-08-28 17:41 ` Krzysztof Kozlowski
2025-08-28 17:40 ` Krzysztof Kozlowski
2025-08-28 18:27 ` Bart Van Assche
2025-08-26 15:08 ` [PATCH V3 2/4] ufs: ufs-qcom: Remove redundant re-assignment to hs_rate Ram Kumar Dwivedi
2025-08-26 15:08 ` [PATCH V3 3/4] ufs: pltfrm: Allow limiting HS gear and rate via DT Ram Kumar Dwivedi
2025-08-26 15:08 ` [PATCH V3 4/4] ufs: ufs-qcom: Add support for limiting HS gear and rate Ram Kumar Dwivedi
2025-08-26 15:37 ` Bart Van Assche [this message]
2025-08-28 16:28 ` Ram Kumar Dwivedi
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=db0a8b86-b048-489b-9b23-6987f48e9419@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_rdwivedi@quicinc.com \
--cc=robh@kernel.org \
/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®