From: Stanley Chu <stanley.chu@mediatek.com>
To: Bean Huo <huobean@gmail.com>
Cc: <alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
<asutoshd@codeaurora.org>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <beanhuo@micron.com>,
<bvanassche@acm.org>, <tomas.winkler@intel.com>,
<cang@codeaurora.org>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] scsi: ufs: Changes comment in the function ufshcd_wb_probe()
Date: Mon, 7 Dec 2020 13:19:21 +0800 [thread overview]
Message-ID: <1607318361.3580.3.camel@mtkswgap22> (raw)
In-Reply-To: <20201206101335.3418-4-huobean@gmail.com>
On Sun, 2020-12-06 at 11:13 +0100, Bean Huo wrote:
> From: Bean Huo <beanhuo@micron.com>
>
> USFHCD supports WriteBooster "LU dedicated buffer” mode and
> “shared buffer” mode both, so changes the comment in the
> function ufshcd_wb_probe().
>
> Signed-off-by: Bean Huo <beanhuo@micron.com>
> Reviewed-by: Can Guo <cang@codeaurora.org>
Reviewed-by: Stanley Chu <stanley.chu@mediatek.com>
prev parent reply other threads:[~2020-12-07 5:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 10:13 [PATCH v2 0/3] Three changes for UFS WriteBooster Bean Huo
2020-12-06 10:13 ` [PATCH v2 1/3] scsi: ufs: Add "wb_on" sysfs node to control WB on/off Bean Huo
2020-12-07 6:51 ` Avri Altman
2020-12-07 6:55 ` Stanley Chu
2020-12-08 7:13 ` Can Guo
2020-12-08 10:54 ` Bean Huo
2020-12-06 10:13 ` [PATCH v2 2/3] scsi: ufs: Keep device active mode only fWriteBoosterBufferFlushDuringHibernate == 1 Bean Huo
2020-12-07 5:36 ` Stanley Chu
2020-12-07 15:19 ` Stanley Chu
2020-12-07 8:02 ` Avri Altman
2020-12-07 11:18 ` Bean Huo
2020-12-08 9:05 ` Avri Altman
2020-12-08 9:41 ` Bean Huo
2020-12-06 10:13 ` [PATCH v2 3/3] scsi: ufs: Changes comment in the function ufshcd_wb_probe() Bean Huo
2020-12-07 5:19 ` Stanley Chu [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=1607318361.3580.3.camel@mtkswgap22 \
--to=stanley.chu@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tomas.winkler@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.