From: Bart Van Assche <bvanassche@acm.org>
To: Alexey Charkov <alchark@flipper.net>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Bean Huo <beanhuo@micron.com>, Can Guo <can.guo@oss.qualcomm.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] scsi: ufs: core: Fix RPMB region size detection for UFS 2.2
Date: Thu, 5 Feb 2026 08:08:40 -0800 [thread overview]
Message-ID: <acc28d2d-3a85-4fba-8c15-fb956c34edf0@acm.org> (raw)
In-Reply-To: <20260205-ufs-rpmb-v2-1-5e1572ee52bf@flipper.net>
On 2/5/26 12:30 AM, Alexey Charkov wrote:
> @@ -5249,6 +5250,20 @@ static void ufshcd_lu_init(struct ufs_hba *hba, struct scsi_device *sdev)
> hba->dev_info.rpmb_region_size[1] = desc_buf[RPMB_UNIT_DESC_PARAM_REGION1_SIZE];
> hba->dev_info.rpmb_region_size[2] = desc_buf[RPMB_UNIT_DESC_PARAM_REGION2_SIZE];
> hba->dev_info.rpmb_region_size[3] = desc_buf[RPMB_UNIT_DESC_PARAM_REGION3_SIZE];
Executing the above code if (hba->dev_info.wspecversion <= 0x0220) is
risky, isn't it?
> + if (hba->dev_info.wspecversion <= 0x0220) {
> + /* These older spec chips have only one RPMB region,
> + * sized between 128 kB minimum and 16 MB maximum.
> + * No per region size fields are provided, so get it
> + * from the logical block count and size fields for
> + * compatibility
> + */
Please follow the Linux kernel coding style for source code comments.
From Documentation/process/coding-style.rst:
The preferred style for long (multi-line) comments is:
.. code-block:: c
/*
* This is the preferred style for multi-line
* comments in the Linux kernel source code.
* Please use it consistently.
*
* Description: A column of asterisks on the left side,
* with beginning and ending almost-blank lines.
*/
Thanks,
Bart.
next prev parent reply other threads:[~2026-02-05 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 8:30 Alexey Charkov
2026-02-05 16:08 ` Bart Van Assche [this message]
2026-02-06 6:49 ` Alexey Charkov
2026-02-09 14:51 ` Bean Huo
2026-02-09 15:18 ` Alexey Charkov
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=acc28d2d-3a85-4fba-8c15-fb956c34edf0@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alchark@flipper.net \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=can.guo@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.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®