mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
	Richard Weinberger <richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] ubifs: fix typo in comment
Date: Thu, 22 Oct 2026 19:41:06 +0800	[thread overview]
Message-ID: <f406a1a9-2bae-e39b-7d7d-62ca43f68937@huawei.com> (raw)
In-Reply-To: <20261022112640.11822-1-alexander.stein@ew.tq-group.com>

在 2026/10/22 19:26, Alexander Stein 写道:
> Small typo which stayed hidden so far. Fix it.
> 
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
>   fs/ubifs/scan.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/fs/ubifs/scan.c b/fs/ubifs/scan.c
> index cbff2d800e27a..50740e9dabf73 100644
> --- a/fs/ubifs/scan.c
> +++ b/fs/ubifs/scan.c
> @@ -245,7 +245,7 @@ void ubifs_scanned_corruption(const struct ubifs_info *c, int lnum, int offs,
>    *
>    * This function scans LEB number @lnum and returns complete information about
>    * its contents. Returns the scanned information in case of success and,
> - * %-EUCLEAN if the LEB neads recovery, and other negative error codes in case
> + * %-EUCLEAN if the LEB needs recovery, and other negative error codes in case
>    * of failure.
>    *
>    * If @quiet is non-zero, this function does not print large and scary
> 


      reply	other threads:[~2026-10-22 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 11:26 Alexander Stein
2026-10-22 11:41 ` Zhihao Cheng [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=f406a1a9-2bae-e39b-7d7d-62ca43f68937@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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®