From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arthur Simchaev <Arthur.Simchaev@wdc.com>
Cc: martin.petersen@oracle.com, beanhuo@micron.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] ufs: core: Always read the descriptors with max length
Date: Fri, 30 Dec 2022 16:50:43 -0500 [thread overview]
Message-ID: <yq1sfgw4l3u.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1670763911-8695-1-git-send-email-Arthur.Simchaev@wdc.com> (Arthur Simchaev's message of "Sun, 11 Dec 2022 15:05:07 +0200")
Arthur,
> Read any descriptor with a maximum size of QUERY_DESC_MAX_SIZE.
> According to the spec the device rerurns the actual size. Thus can
> improve code readability and save CPU cycles. While at it, cleanup
> few leftovers around the descriptor size parameter.
Applied to 6.3/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-12-30 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 13:05 [PATCH v5 0/4] ufs: core: Always read the descriptors with max length Arthur Simchaev
2022-12-11 13:05 ` [PATCH v5 1/4] ufs: core: Remove redundant wb check Arthur Simchaev
2022-12-13 5:32 ` Stanley Chu
2022-12-11 13:05 ` [PATCH v5 2/4] ufs: core: Remove redundant desc_size variable from hba Arthur Simchaev
2022-12-12 0:11 ` Bart Van Assche
2022-12-11 13:05 ` [PATCH v5 3/4] ufs: core: Remove len parameter from ufshcd_set_active_icc_lvl Arthur Simchaev
2022-12-11 13:05 ` [PATCH v5 4/4] ufs: core: Remove ufshcd_map_desc_id_to_length function Arthur Simchaev
2022-12-12 0:18 ` Bart Van Assche
2022-12-12 9:10 ` Arthur Simchaev
2022-12-12 19:25 ` Bart Van Assche
2022-12-12 19:26 ` Bart Van Assche
2022-12-30 21:50 ` Martin K. Petersen [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=yq1sfgw4l3u.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=Arthur.Simchaev@wdc.com \
--cc=beanhuo@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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