From: Bean Huo <huobean@gmail.com>
To: Arthur Simchaev <Arthur.Simchaev@wdc.com>, martin.petersen@oracle.com
Cc: beanhuo@micron.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] ufs: core: Remove len parameter from ufshcd_set_active_icc_lvl
Date: Mon, 14 Nov 2022 13:19:28 +0100 [thread overview]
Message-ID: <4e205f57-673f-bd7b-1c04-5f3c8db0b054@gmail.com> (raw)
In-Reply-To: <1667399353-10228-4-git-send-email-Arthur.Simchaev@wdc.com>
Arthur,
On 02.11.22 3:29 PM, Arthur Simchaev wrote:
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index aa46292..9cc3abd 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -7386,7 +7386,7 @@ static u32 ufshcd_get_max_icc_level(int sup_curr_uA, u32 start_scan,
> * Returns calculated ICC level
> */
> static u32 ufshcd_find_max_sup_active_icc_level(struct ufs_hba *hba,
> - const u8 *desc_buf, int len)
> + const u8 *desc_buf)
'len' description of 'ufshcd_find_max_sup_active_icc_level()' should be
removed as well.
Kind regards,
Bean
next prev parent reply other threads:[~2022-11-14 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 14:29 [PATCH v2 0/4] ufs: core: Always read the descriptors with max length Arthur Simchaev
2022-11-02 14:29 ` [PATCH v2 1/4] ufs: core: Remove redundant wb check Arthur Simchaev
2022-11-02 14:29 ` [PATCH v2 2/4] ufs: core: Remove redundant desc_size variable from hba Arthur Simchaev
2022-11-11 15:45 ` Bean Huo
2022-11-13 13:33 ` Arthur Simchaev
2022-11-02 14:29 ` [PATCH v2 3/4] ufs: core: Remove len parameter from ufshcd_set_active_icc_lvl Arthur Simchaev
2022-11-14 12:19 ` Bean Huo [this message]
2022-11-15 12:49 ` Arthur Simchaev
2022-11-02 14:29 ` [PATCH v2 4/4] ufs: core: Remove ufshcd_map_desc_id_to_length function Arthur Simchaev
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=4e205f57-673f-bd7b-1c04-5f3c8db0b054@gmail.com \
--to=huobean@gmail.com \
--cc=Arthur.Simchaev@wdc.com \
--cc=beanhuo@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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