From: Bart Van Assche <bvanassche@acm.org>
To: Huan Tang <tanghuan@vivo.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, peter.wang@mediatek.com,
manivannan.sadhasivam@linaro.org, quic_nguyenb@quicinc.com,
luhongfei@vivo.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: opensource.kernel@vivo.com, Wenxing Cheng <wenxing.cheng@vivo.com>
Subject: Re: [PATCH v3] ufs: core: Add HID support
Date: Mon, 19 May 2025 14:02:41 -0700 [thread overview]
Message-ID: <08e67735-d5b0-47d0-b476-c22a3b5acdda@acm.org> (raw)
In-Reply-To: <20250519022912.292-1-tanghuan@vivo.com>
On 5/18/25 7:29 PM, Huan Tang wrote:
> Follow JESD220G, support HID(Host Initiated Defragmentation)
> through sysfs, the relevant sysfs nodes are as follows:
> 1.analysis_trigger
> 2.defrag_trigger
> 3.fragmented_size
> 4.defrag_size
> 5.progress_ratio
> 6.state
> The detailed definition of the six nodes can be found in the sysfs
> documentation.
>
> HID's execution policy is given to user-space.
>
> Changelog
> ===
> v2 - > v3:
> 1.Remove the "ufs_" prefix from directory name
> 2.Remove the "hid_" prefix from node names
> 3.Make "ufs" appear only once in the HID group name
> 4.Add "is_visible" callback for "ufs_sysfs_hid_group"
> v1 - > v2:
> 1.Refactor the HID code according to Bart and Peter and
> Arvi's suggestions
>
> v2
> https://lore.kernel.org/all/20250512131519.138-1-tanghuan@vivo.com/
> v1
> https://lore.kernel.org/all/20250417125008.123-1-tanghuan@vivo.com/
>
> Signed-off-by: Huan Tang <tanghuan@vivo.com>
> Signed-off-by: Wenxing Cheng <wenxing.cheng@vivo.com>
> ---
The patch changelog should occur below the three hyphens (---) such that
it doesn't end up in the kernel changelog. Otherwise this patch looks
good to me. Hence:
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
prev parent reply other threads:[~2025-05-19 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 2:29 Huan Tang
2025-05-19 21:02 ` Bart Van Assche [this message]
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=08e67735-d5b0-47d0-b476-c22a3b5acdda@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.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=luhongfei@vivo.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=opensource.kernel@vivo.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.com \
--cc=tanghuan@vivo.com \
--cc=wenxing.cheng@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
all inboxes | Powered by JetHome®