From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Dominique Martinet <asmadeus@codewreck.org>,
Tingmao Wang <m@maowtm.org>,
v9fs@lists.linux.dev
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: fs/9p: Add missing "not" in cache documentation
Date: Mon, 31 Mar 2025 09:54:09 +0200 [thread overview]
Message-ID: <36322483.C5m3dU8G8V@silver> (raw)
In-Reply-To: <20250330213443.98434-1-m@maowtm.org>
On Sunday, March 30, 2025 11:34:42 PM CEST Tingmao Wang wrote:
> A quick fix for what I assume is a typo.
>
> Signed-off-by: Tingmao Wang <m@maowtm.org>
> ---
Reviewed-by: Christian Schoenebeck <linux_oss@crudebyte.com>
> Documentation/filesystems/9p.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/filesystems/9p.rst b/Documentation/filesystems/9p.rst
> index 2bbf68b56b0d..c9f0274c808e 100644
> --- a/Documentation/filesystems/9p.rst
> +++ b/Documentation/filesystems/9p.rst
> @@ -165,8 +165,8 @@ Options
> do not necessarily validate cached values on the server. In other
> words changes on the server are not guaranteed to be reflected
> on the client system. Only use this mode of operation if you
> - have an exclusive mount and the server will modify the filesystem
> - underneath you.
> + have an exclusive mount and the server will not modify the
> + filesystem underneath you.
>
> debug=n specifies debug level. The debug level is a bitmask.
>
>
> base-commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557
>
prev parent reply other threads:[~2025-03-31 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 21:34 [PATCH] docs: fs/9p: Add missing "not" in cache documentation Tingmao Wang
2025-03-30 21:43 ` Dominique Martinet
2025-03-31 7:54 ` Christian Schoenebeck [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=36322483.C5m3dU8G8V@silver \
--to=linux_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=m@maowtm.org \
--cc=v9fs@lists.linux.dev \
/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