From: "Asutosh Das (asd)" <asutoshd@codeaurora.org>
To: Stanley Chu <stanley.chu@mediatek.com>,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com
Cc: beanhuo@micron.com, cang@codeaurora.org, matthias.bgg@gmail.com,
bvanassche@acm.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Virtual_Global_UFS_Upstream@mediatek.com
Subject: Re: [PATCH v4 0/4] scsi: ufs: Fix WriteBooster and cleanup UFS driver
Date: Tue, 26 May 2020 10:25:41 -0700 [thread overview]
Message-ID: <a18ed057-e35b-b1b9-9ce2-718d7c3961fd@codeaurora.org> (raw)
In-Reply-To: <20200522083212.4008-1-stanley.chu@mediatek.com>
On 5/22/2020 1:32 AM, Stanley Chu wrote:
> Hi,
>
> This patch set fixes some WriteBooster issues and do small cleanup in UFS driver
>
> v3 -> v4
> - Squash patch [4] and [5] (Asutosh)
> - Fix commit message in patch [4]
>
> v2 -> v3
> - Introduce patch [5] to fix possible VCC power drain during runtime suspend (Asutosh)
>
> v1 -> v2
> - Remove dummy new line in patch [4] (Asutosh)
> - Add more limitation to allow WriteBooster flush during Hibern8 in runtime-suspend. Now the device power mode is kept as Active power mode only if link is put in Hibern8 or Auto-Hibern8 is enabled during runtime-suspend (Asutosh)
>
> Stanley Chu (4):
> scsi: ufs: Remove unnecessary memset for dev_info
> scsi: ufs: Allow WriteBooster on UFS 2.2 devices
> scsi: ufs: Fix index of attributes query for WriteBooster feature
> scsi: ufs: Fix WriteBooster flush during runtime suspend
>
> drivers/scsi/ufs/ufs-sysfs.c | 13 ++++-
> drivers/scsi/ufs/ufs.h | 2 +-
> drivers/scsi/ufs/ufshcd.c | 99 +++++++++++++++++++++++++-----------
> drivers/scsi/ufs/ufshcd.h | 3 +-
> 4 files changed, 82 insertions(+), 35 deletions(-)
>
This set looks good to me.
Reviewed-by: Asutosh Das <asutoshd@codeaurora.org>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-05-26 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 8:32 [PATCH v4 0/4] scsi: ufs: Fix WriteBooster and cleanup UFS driver Stanley Chu
2020-05-22 8:32 ` [PATCH v4 1/4] scsi: ufs: Remove unnecessary memset for dev_info Stanley Chu
2020-05-22 8:32 ` [PATCH v4 2/4] scsi: ufs: Allow WriteBooster on UFS 2.2 devices Stanley Chu
2020-05-22 8:32 ` [PATCH v4 3/4] scsi: ufs: Fix index of attributes query for WriteBooster feature Stanley Chu
2020-05-22 8:32 ` [PATCH v4 4/4] scsi: ufs: Fix WriteBooster flush during runtime suspend Stanley Chu
2020-05-26 17:25 ` Asutosh Das (asd) [this message]
2020-05-27 2:12 ` [PATCH v4 0/4] scsi: ufs: Fix WriteBooster and cleanup UFS driver 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=a18ed057-e35b-b1b9-9ce2-718d7c3961fd@codeaurora.org \
--to=asutoshd@codeaurora.org \
--cc=Virtual_Global_UFS_Upstream@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=stanley.chu@mediatek.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).