From: "Darrick J. Wong" <djwong@kernel.org>
To: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-xfs@vger.kernel.org,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH] Documentation: iomap: fix a typo
Date: Tue, 20 Aug 2024 09:15:37 -0700 [thread overview]
Message-ID: <20240820161537.GS865349@frogsfrogsfrogs> (raw)
In-Reply-To: <20240820161329.1293718-1-kernel@pankajraghav.com>
On Tue, Aug 20, 2024 at 06:13:29PM +0200, Pankaj Raghav (Samsung) wrote:
> From: Pankaj Raghav <p.raghav@samsung.com>
>
> Change voidw -> void.
>
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
Heh, whoopsw.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> Documentation/filesystems/iomap/design.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/iomap/design.rst b/Documentation/filesystems/iomap/design.rst
> index 37594e1c5914..7261b1b2c379 100644
> --- a/Documentation/filesystems/iomap/design.rst
> +++ b/Documentation/filesystems/iomap/design.rst
> @@ -165,7 +165,7 @@ structure below:
> u16 flags;
> struct block_device *bdev;
> struct dax_device *dax_dev;
> - voidw *inline_data;
> + void *inline_data;
> void *private;
> const struct iomap_folio_ops *folio_ops;
> u64 validity_cookie;
> --
> 2.44.1
>
>
next prev parent reply other threads:[~2024-08-20 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 16:13 [PATCH] Documentation: iomap: fix a typo Pankaj Raghav (Samsung)
2024-08-20 16:15 ` Darrick J. Wong [this message]
2024-08-21 0:05 ` David Sterba
2024-08-21 7:15 ` Pankaj Raghav (Samsung)
2024-09-12 11:52 ` Pankaj Raghav (Samsung)
2024-09-12 12:07 ` Christian Brauner
2024-09-17 16:19 ` 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=20240820161537.GS865349@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=kernel@pankajraghav.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=p.raghav@samsung.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