From: Bart Van Assche <bvanassche@acm.org>
To: Lu Hongfei <luhongfei@vivo.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Bean Huo <beanhuo@micron.com>, Can Guo <quic_cang@quicinc.com>,
Arthur Simchaev <arthur.simchaev@wdc.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Asutosh Das <quic_asutoshd@quicinc.com>,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
Po-Wen Kao <powen.kao@mediatek.com>,
Eric Biggers <ebiggers@google.com>,
Keoseong Park <keosung.park@samsung.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v3 0/3] scsi: ufs: core: support WB buffer resize function
Date: Thu, 19 Oct 2023 11:20:41 -0700 [thread overview]
Message-ID: <ec1a2b51-6b46-441d-99e2-8e5bc48ba2d2@acm.org> (raw)
In-Reply-To: <86e5cc25-80f7-451b-9067-a220c7a2c39e@vivo.com>
On 10/18/23 21:50, Lu Hongfei wrote:
> Are there any new developments in this group of patches?
The JEDEC ballot about resizing the WriteBooster buffer has not yet been
approved. Please wait with posting patches that implement support for a
JEDEC feature until agreement has been reached in JEDEC.
Thanks,
Bart.
next prev parent reply other threads:[~2023-10-19 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 5:57 Lu Hongfei
2023-09-11 5:57 ` [PATCH v3 1/3] scsi: ufs: core: add wb buffer resize related attr_idn Lu Hongfei
2023-09-11 5:57 ` [PATCH v3 2/3] scsi: ufs: core: Add sysfs attribute to control WB buffer resize function Lu Hongfei
2023-09-11 5:57 ` [PATCH v3 3/3] scsi: ufs: core: Add sysfs attributes to get the hint information and status of WB buffer resize Lu Hongfei
2023-10-19 3:53 ` [PATCH v3 0/3] scsi: ufs: core: support WB buffer resize function 路红飞
2023-10-19 4:50 ` Lu Hongfei
2023-10-19 18:20 ` Bart Van Assche [this message]
2023-10-20 7:11 ` Lu Hongfei
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=ec1a2b51-6b46-441d-99e2-8e5bc48ba2d2@acm.org \
--to=bvanassche@acm.org \
--cc=alim.akhtar@samsung.com \
--cc=arthur.simchaev@wdc.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=ebiggers@google.com \
--cc=jejb@linux.ibm.com \
--cc=keosung.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luhongfei@vivo.com \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=opensource.kernel@vivo.com \
--cc=powen.kao@mediatek.com \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.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
all inboxes | Powered by JetHome®