Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Bean Huo <huobean@gmail.com>, Huan Tang <tanghuan@vivo.com>,
	linux-scsi@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v2] ufs: core: Add WB buffer resize support
Date: Mon, 28 Oct 2024 11:37:41 -0700	[thread overview]
Message-ID: <04e443d0-2968-4d63-b05e-ddb7b2aa5680@acm.org> (raw)
In-Reply-To: <e992d83526fe722af8cef1b9ca737c8d0646417a.camel@gmail.com>

On 10/26/24 12:40 PM, Bean Huo wrote:
> I saw that "Both UFS 4.1 and UFS 5.0 are currently in development" have
> not been officially published yet. Are you keen to incorporate features
> based on an unpublished standard?

Hi Bean,

UFS WG members approved the WB buffer resize functionality through the
JEDEC voting process about one year ago. Isn't that sufficient to
implement this functionality in the kernel? See also the JC-64.1
December 7, 2023 meeting minutes.

Thanks,

Bart.


  reply	other threads:[~2024-10-28 18:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26  0:44 [PATCH v2] ufs: core: Add WB buffer resize support Huan Tang
2024-10-26 17:03 ` kernel test robot
2024-10-26 17:44 ` kernel test robot
2024-10-26 19:40 ` Bean Huo
2024-10-28 18:37   ` Bart Van Assche [this message]
2024-10-28 20:04     ` [EXT] " Bean Huo
2024-10-28 20:10       ` Bart Van Assche
2024-10-28 20:17         ` Bean Huo
2024-10-29  2:53           ` Huan Tang
2024-10-29  3:11           ` Huan Tang
2024-10-29 10:17             ` Bean Huo
2024-10-29 12:03               ` Huan Tang
2024-10-29 13:18                 ` Bean Huo
2024-10-29 16:56                   ` Bart Van Assche
2024-10-29 18:44                     ` Bean Huo
2024-10-30  9:37                       ` Huan Tang
2024-10-30 15:13                         ` Bean Huo

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=04e443d0-2968-4d63-b05e-ddb7b2aa5680@acm.org \
    --to=bvanassche@acm.org \
    --cc=huobean@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=tanghuan@vivo.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