linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Huan Tang <tanghuan@vivo.com>
Cc: huobean@gmail.com, cang@qti.qualcomm.com,
	linux-scsi@vger.kernel.org, opensource.kernel@vivo.com,
	richardp@quicinc.com, luhongfei@vivo.com
Subject: Re: [PATCH v11] ufs: core: Add WB buffer resize support
Date: Fri, 11 Apr 2025 12:30:16 -0700	[thread overview]
Message-ID: <04ccb1a0-e29e-41b7-ad3d-6e12f66ceff9@acm.org> (raw)
In-Reply-To: <20250411092924.1116-1-tanghuan@vivo.com>

On 4/11/25 2:29 AM, Huan Tang wrote:
> Follow JESD220G, Support WB buffer resize function through sysfs,
> the host can obtain resize hint and resize status, and enable the
> resize operation. To achieve this goals, three sysfs nodes have
> been added:
> 	1. wb_resize_enable
> 	2. wb_resize_hint
> 	3. wb_resize_status
> The detailed definition of the three nodes can be found in the sysfs
> documentation.

Please do not use the git send-email --in-reply-to option when posting a
new version of a patch or a new version of a patch series - this may
cause patches to be overlooked. Since this patch looks fine to me:

Reviewed-by: Bart Van Assche <bvanassche@acm.org>

  reply	other threads:[~2025-04-11 19:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 13:52 [PATCH v3] ufs: core: Add WB buffer resize support Huan Tang
2024-10-28 19:50 ` Bart Van Assche
2024-11-01  9:37   ` Huan Tang
2024-11-01 16:23     ` Bart Van Assche
2024-11-04 14:27       ` Huan Tang
2024-11-04 17:28         ` Bart Van Assche
2024-11-05  2:31           ` Huan Tang
2025-04-11  9:29       ` [PATCH v11] " Huan Tang
2025-04-11 19:30         ` Bart Van Assche [this message]
2025-04-12  1:38         ` Martin K. Petersen
2025-04-23  8:06         ` Peter Wang (王信友)
2025-04-23  8:26           ` Huan Tang

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=04ccb1a0-e29e-41b7-ad3d-6e12f66ceff9@acm.org \
    --to=bvanassche@acm.org \
    --cc=cang@qti.qualcomm.com \
    --cc=huobean@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=luhongfei@vivo.com \
    --cc=opensource.kernel@vivo.com \
    --cc=richardp@quicinc.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;
as well as URLs for NNTP newsgroup(s).