From: Bean Huo <huobean@gmail.com>
To: Huan Tang <tanghuan@vivo.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com,
bvanassche@acm.org, James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, beanhuo@micron.com,
luhongfei@vivo.com, quic_cang@quicinc.com,
keosung.park@samsung.com, viro@zeniv.linux.org.uk,
quic_mnaresh@quicinc.com, peter.wang@mediatek.com,
manivannan.sadhasivam@linaro.org, quic_nguyenb@quicinc.com,
linux@weissschuh.net, ebiggers@google.com,
minwoo.im@samsung.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v8] ufs: core: Add WB buffer resize support
Date: Wed, 02 Apr 2025 10:43:09 +0200 [thread overview]
Message-ID: <5e067f1eecb2098c9c2368dc8a2005c1567198b0.camel@gmail.com> (raw)
In-Reply-To: <20250402075710.224-1-tanghuan@vivo.com>
On Wed, 2025-04-02 at 15:57 +0800, Huan Tang wrote:
> +static const char *ufs_wb_resize_status_to_string(enum
> wb_resize_status status)
> +{
> + switch (status) {
> + case WB_RESIZE_STATUS_IDLE:
> + return "idle";
> + case WB_RESIZE_STATUS_IN_PROGRESS:
> + return "in_progress";
> + case WB_RESIZE_STATUS_COMPLETE_SUCCESS:
> + return "complete_success";
> + case WB_RESIZE_STATUS_GENERAL_FAIL:
> + return "gerneral_fail";
Typo: "gerneral_fail" --> general_fail
next prev parent reply other threads:[~2025-04-02 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 7:57 Huan Tang
2025-04-02 8:43 ` Bean Huo [this message]
2025-04-07 8:57 ` Huan Tang
2025-04-02 8:51 ` Bean Huo
2025-04-07 8:56 ` 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=5e067f1eecb2098c9c2368dc8a2005c1567198b0.camel@gmail.com \
--to=huobean@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=ebiggers@google.com \
--cc=keosung.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=luhongfei@vivo.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=minwoo.im@samsung.com \
--cc=opensource.kernel@vivo.com \
--cc=peter.wang@mediatek.com \
--cc=quic_cang@quicinc.com \
--cc=quic_mnaresh@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=tanghuan@vivo.com \
--cc=viro@zeniv.linux.org.uk \
/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®