Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Huan Tang <tanghuan@vivo.com>
To: beanhuo@micron.com
Cc: bvanassche@acm.org, cang@qti.qualcomm.com, huobean@gmail.com,
	linux-scsi@vger.kernel.org, opensource.kernel@vivo.com,
	richardp@quicinc.com, tanghuan@vivo.com
Subject: RE: [EXT] Re: [PATCH v2] ufs: core: Add WB buffer resize support
Date: Tue, 29 Oct 2024 10:53:13 +0800	[thread overview]
Message-ID: <20241029025313.324-1-tanghuan@vivo.com> (raw)
In-Reply-To: <SA6PR08MB10163D9B8FE4BE9DF5A47D9E1DB4A2@SA6PR08MB10163.namprd08.prod.outlook.com>

> I would like to say this actually: committee approval of a ballot does not give a company or individual the ability to disclose the
> feature outside of JEDEC.

> Unless JEDEC has published details relating to a particular feature in a not-yet-board-approved standard, these details should be
> considered proprietary to JEDEC members and not revealed outside of JEDEC until JEDEC board approval has occurred.  For UFS 4.1,
> which will include the WB resize feature. Has not officially published yet.  Before that, there is no public information to release to
> the community.  


> Kind regards,
> Bean

Hi Bean,

JEDEC expects to release it in early November this year. The spec for this feature has been confirmed. 
Do we need to wait until the standard is officially released before discussing this submission?

Thanks
Huan

  reply	other threads:[~2024-10-29  2:53 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
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 [this message]
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=20241029025313.324-1-tanghuan@vivo.com \
    --to=tanghuan@vivo.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=cang@qti.qualcomm.com \
    --cc=huobean@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=richardp@quicinc.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