From: Avri Altman <Avri.Altman@wdc.com>
To: Asutosh Das <asutoshd@codeaurora.org>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: RE: [PATCH v2 0/3] UFS Clock Scaling fixes and enhancements
Date: Wed, 25 Mar 2020 23:18:55 +0000 [thread overview]
Message-ID: <SN6PR04MB4640E428E281A381725CE5E0FCCE0@SN6PR04MB4640.namprd04.prod.outlook.com> (raw)
In-Reply-To: <cover.1585160616.git.asutoshd@codeaurora.org>
Looks good to me.
Thanks,
Avri
>
>
> Enhancements to clock-scaling parameters.
> Few bug fixes to clock-scaling.
>
> Changes since v1:
> - Addressed comments of v1
>
> Asutosh Das (3):
> scsi: ufshcd: Update the set frequency to devfreq
> scsi: ufshcd: Let vendor override devfreq parameters
> scsi: ufs-qcom: Override devfreq parameters
>
> drivers/scsi/ufs/ufs-qcom.c | 25 +++++++++++++++++++++++++
> drivers/scsi/ufs/ufshcd.c | 32 ++++++++++++++++++++++++++++++--
> drivers/scsi/ufs/ufshcd.h | 12 ++++++++++++
> 3 files changed, 67 insertions(+), 2 deletions(-)
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2020-03-25 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 18:28 [PATCH v2 0/3] UFS Clock Scaling fixes and enhancements Asutosh Das
2020-03-25 18:29 ` [PATCH v2 1/3] scsi: ufshcd: Update the set frequency to devfreq Asutosh Das
2020-05-25 22:19 ` Jeffrey Hugo
2020-05-26 17:17 ` Asutosh Das (asd)
2020-05-28 13:53 ` Jeffrey Hugo
2020-03-25 18:29 ` [PATCH v2 2/3] scsi: ufshcd: Let vendor override devfreq parameters Asutosh Das
2020-03-25 18:29 ` [PATCH v2 3/3] scsi: ufs-qcom: Override " Asutosh Das
2020-03-25 23:18 ` Avri Altman [this message]
2020-03-27 2:18 ` [PATCH v2 0/3] UFS Clock Scaling fixes and enhancements Martin K. Petersen
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=SN6PR04MB4640E428E281A381725CE5E0FCCE0@SN6PR04MB4640.namprd04.prod.outlook.com \
--to=avri.altman@wdc.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=linux-arm-msm@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;
as well as URLs for NNTP newsgroup(s).