From: Stanley Chu <stanley.chu@mediatek.com>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"andy.teng@mediatek.com" <andy.teng@mediatek.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"chun-hung.wu@mediatek.com" <chun-hung.wu@mediatek.com>,
"kuohong.wang@mediatek.com" <kuohong.wang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"peter.wang@mediatek.com" <peter.wang@mediatek.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>
Subject: Re: [PATCH v1 3/4] scsi: ufs: add LU Dedicated buffer type support for WriteBooster
Date: Wed, 29 Apr 2020 21:05:06 +0800 [thread overview]
Message-ID: <1588165506.3197.0.camel@mtkswgap22> (raw)
In-Reply-To: <BN7PR08MB5684630793F03282E4C6F3D7DBAD0@BN7PR08MB5684.namprd08.prod.outlook.com>
Hi Bean,
On Wed, 2020-04-29 at 10:39 +0000, Bean Huo (beanhuo) wrote:
> >
> > +/* WriteBooster buffer type */
> > +enum {
> > + WB_TYPE_LU_DEDICATED = 0x0,
> > + WB_TYPE_SINGLE_SHARED = 0x1
> > +};
>
>
> Hi, Stanly
> WB_TYPE_SINGLE_SHARED might be WB_TYPE_SHARED_BUFFER. I think,
> we should try to make the name definition correspond to Spec
Make sense. I will fix this in next version.
Thanks,
Stanley Chu
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-04-29 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 11:13 [PATCH v1 0/4] scsi: ufs: support LU Dedicated buffer type for WriteBooster Stanley Chu
2020-04-28 11:13 ` [PATCH v1 1/4] scsi: ufs: allow legacy UFS devices to enable WriteBooster Stanley Chu
2020-04-29 10:18 ` [EXT] " Bean Huo (beanhuo)
2020-04-28 11:13 ` [PATCH v1 2/4] scsi: ufs: add "index" in parameter list of ufshcd_query_flag() Stanley Chu
2020-04-29 9:24 ` [EXT] " Bean Huo (beanhuo)
2020-04-28 11:13 ` [PATCH v1 3/4] scsi: ufs: add LU Dedicated buffer type support for WriteBooster Stanley Chu
2020-04-29 10:39 ` [EXT] " Bean Huo (beanhuo)
2020-04-29 13:05 ` Stanley Chu [this message]
2020-04-28 11:13 ` [PATCH v1 4/4] scsi: ufs-mediatek: enable WriteBooster capability Stanley Chu
2020-04-29 10:19 ` [EXT] " Bean Huo (beanhuo)
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=1588165506.3197.0.camel@mtkswgap22 \
--to=stanley.chu@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@mediatek.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=peter.wang@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).