From: "Darrick J. Wong" <djwong@kernel.org>
To: Bingwu Zhang <xtex@envs.net>
Cc: Jonathan Corbet <corbet@lwn.net>,
Miklos Szeredi <miklos@szeredi.hu>, Bingwu Zhang <xtex@aosc.io>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-xfs@vger.kernel.org, ~xtex/staging@lists.sr.ht
Subject: Re: [PATCH] Documentation: filesystems: fix two misspells
Date: Wed, 11 Dec 2024 09:40:29 -0800 [thread overview]
Message-ID: <20241211174029.GC6698@frogsfrogsfrogs> (raw)
In-Reply-To: <20241208035447.162465-2-xtex@envs.net>
On Sun, Dec 08, 2024 at 11:54:47AM +0800, Bingwu Zhang wrote:
> From: Bingwu Zhang <xtex@aosc.io>
>
> This fixes two small misspells in the filesystems documentation.
>
> Signed-off-by: Bingwu Zhang <xtex@aosc.io>
Yep, typoes happun, thanks for the patch.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> I found these typos when learning about OverlayFS recently.
> ---
> Documentation/filesystems/iomap/operations.rst | 2 +-
> Documentation/filesystems/overlayfs.rst | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/filesystems/iomap/operations.rst b/Documentation/filesystems/iomap/operations.rst
> index ef082e5a4e0c..2c7f5df9d8b0 100644
> --- a/Documentation/filesystems/iomap/operations.rst
> +++ b/Documentation/filesystems/iomap/operations.rst
> @@ -104,7 +104,7 @@ iomap calls these functions:
>
> For the pagecache, races can happen if writeback doesn't take
> ``i_rwsem`` or ``invalidate_lock`` and updates mapping information.
> - Races can also happen if the filesytem allows concurrent writes.
> + Races can also happen if the filesystem allows concurrent writes.
> For such files, the mapping *must* be revalidated after the folio
> lock has been taken so that iomap can manage the folio correctly.
>
> diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst
> index 4c8387e1c880..d2a277e3976e 100644
> --- a/Documentation/filesystems/overlayfs.rst
> +++ b/Documentation/filesystems/overlayfs.rst
> @@ -156,7 +156,7 @@ A directory is made opaque by setting the xattr "trusted.overlay.opaque"
> to "y". Where the upper filesystem contains an opaque directory, any
> directory in the lower filesystem with the same name is ignored.
>
> -An opaque directory should not conntain any whiteouts, because they do not
> +An opaque directory should not contain any whiteouts, because they do not
> serve any purpose. A merge directory containing regular files with the xattr
> "trusted.overlay.whiteout", should be additionally marked by setting the xattr
> "trusted.overlay.opaque" to "x" on the merge directory itself.
>
> base-commit: 7503345ac5f5e82fd9a36d6e6b447c016376403a
> --
> 2.47.1
>
next prev parent reply other threads:[~2024-12-11 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-08 3:54 [PATCH] Documentation: filesystems: fix two misspells Bingwu Zhang
2024-12-11 17:40 ` Darrick J. Wong [this message]
2024-12-11 19:58 ` Matthew Wilcox
2024-12-13 15:47 ` Jonathan Corbet
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=20241211174029.GC6698@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=xtex@aosc.io \
--cc=xtex@envs.net \
--cc=~xtex/staging@lists.sr.ht \
/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