mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Hemanth Selam <hemanth.selam@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: ubi: fix typo "occured" in comment
Date: Mon, 7 Sep 2026 14:47:28 +0800	[thread overview]
Message-ID: <de859d54-615f-8e64-79df-9d207cde6d1b@huawei.com> (raw)
In-Reply-To: <20260907063111.19769-1-hemanth.selam@gmail.com>

在 2026/9/7 14:31, Hemanth Selam 写道:
> Correct "occured" to "occurred", reported by scripts/checkpatch.pl using
> the misspelling list in scripts/spelling.txt.  Only touches comments, no
> code changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
>   drivers/mtd/ubi/wl.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 

Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/drivers/mtd/ubi/wl.c b/drivers/mtd/ubi/wl.c
> index 5a0db928a90e..44237de52250 100644
> --- a/drivers/mtd/ubi/wl.c
> +++ b/drivers/mtd/ubi/wl.c
> @@ -1486,7 +1486,7 @@ static bool scrub_possible(struct ubi_device *ubi, struct ubi_wl_entry *e)
>    * @pnum: the physical eraseblock to schedule
>    * @force: don't read the block, assume bitflips happened and take action.
>    *
> - * This function reads the given eraseblock and checks if bitflips occured.
> + * This function reads the given eraseblock and checks if bitflips occurred.
>    * In case of bitflips, the eraseblock is scheduled for scrubbing.
>    * If scrubbing is forced with @force, the eraseblock is not read,
>    * but scheduled for scrubbing right away.
> 


      reply	other threads:[~2026-09-07  6:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  6:31 Hemanth Selam
2026-09-07  6:47 ` 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=de859d54-615f-8e64-79df-9d207cde6d1b@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=hemanth.selam@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.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®