From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Huan Tang <tanghuan@vivo.com>
Cc: alim.akhtar@samsung.com, avri.altman@wdc.com, bvanassche@acm.org,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, beanhuo@micron.com,
peter.wang@mediatek.com, quic_nguyenb@quicinc.com,
quic_ziqichen@quicinc.com, keosung.park@samsung.com,
viro@zeniv.linux.org.uk, gwendal@chromium.org,
manivannan.sadhasivam@linaro.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, opensource.kernel@vivo.com,
Wenxing Cheng <wenxing.cheng@vivo.com>,
Bean Huo <huobean@gmail.com>
Subject: Re: [PATCH v6] ufs: core: Add HID support
Date: Mon, 09 Jun 2025 21:52:43 -0400 [thread overview]
Message-ID: <yq1v7p45pny.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250523064604.800-1-tanghuan@vivo.com> (Huan Tang's message of "Fri, 23 May 2025 14:46:04 +0800")
Huan,
> 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.
Applied to 6.17/scsi-staging, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2025-06-10 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 6:46 [PATCH v6] ufs: core: Add HID support Huan Tang
2025-05-27 21:38 ` Bart Van Assche
2025-05-29 3:08 ` Yangtao Li
2025-06-10 1:52 ` Martin K. Petersen [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=yq1v7p45pny.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=gwendal@chromium.org \
--cc=huobean@gmail.com \
--cc=keosung.park@samsung.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=manivannan.sadhasivam@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=opensource.kernel@vivo.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_ziqichen@quicinc.com \
--cc=tanghuan@vivo.com \
--cc=viro@zeniv.linux.org.uk \
--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