From: "Darrick J. Wong" <djwong@kernel.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] iomap: fix typo "metdata" in comment
Date: Fri, 4 Sep 2026 08:11:28 -0700 [thread overview]
Message-ID: <20260904151128.GH6047@frogsfrogsfrogs> (raw)
In-Reply-To: <20260904103825.8752-2-hemanth.selam@gmail.com>
On Fri, Sep 04, 2026 at 04:08:22PM +0530, Hemanth Selam wrote:
> Correct "metdata" to "metadata", 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>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/iomap/direct-io.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/iomap/direct-io.c b/fs/iomap/direct-io.c
> index 8b4039d16ce8..b70f86292049 100644
> --- a/fs/iomap/direct-io.c
> +++ b/fs/iomap/direct-io.c
> @@ -505,7 +505,7 @@ static int iomap_dio_bio_iter(struct iomap_iter *iter, struct iomap_dio *dio)
> * We can only do inline completion for pure overwrites that
> * don't require additional I/O at completion time.
> *
> - * This rules out writes that need zeroing or metdata updates to
> + * This rules out writes that need zeroing or metadata updates to
> * convert unwritten or shared extents.
> *
> * Writes that extend i_size are also not supported, but this is
> --
> 2.48.1
>
>
next prev parent reply other threads:[~2026-09-04 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260904103825.8752-1-hemanth.selam@gmail.com>
2026-09-04 10:38 ` [PATCH 1/2] iomap: fix typo "metdata" in comment Hemanth Selam
2026-09-04 15:11 ` Darrick J. Wong [this message]
2026-09-04 10:38 ` [PATCH 2/2] iomap: fix repeated word 'the' " Hemanth Selam
2026-09-04 15:11 ` Darrick J. Wong
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=20260904151128.GH6047@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=hemanth.selam@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.