From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux NFS <linux-nfs@vger.kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Mike Snitzer <snitzer@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/3] NFSD IO MODES documentation fixes
Date: Wed, 3 Dec 2025 08:09:08 +0700 [thread overview]
Message-ID: <20251203010911.14234-1-bagasdotme@gmail.com> (raw)
Hi,
Here are fixes for NFSD IO modes documentation as reported in linux-next [1].
Enjoy!
[1]: https://lore.kernel.org/linux-next/20251202152506.7a2d2d41@canb.auug.org.au/
Bagas Sanjaya (3):
NFSD: Add toctree entry for NFSD IO modes docs
NFSD: nfsd-io-modes: Wrap shell snippets in literal code blocks
NFSD: nfsd-io-modes: Separate lists
Documentation/filesystems/nfs/index.rst | 1 +
.../filesystems/nfs/nfsd-io-modes.rst | 33 ++++++++++++-------
2 files changed, 22 insertions(+), 12 deletions(-)
base-commit: fa8d4e6784d1b6a6eaa3911bac993181631d2856
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-12-03 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 1:09 Bagas Sanjaya [this message]
2025-12-03 1:09 ` [PATCH 1/3] NFSD: Add toctree entry for NFSD IO modes docs Bagas Sanjaya
2025-12-03 1:09 ` [PATCH 2/3] NFSD: nfsd-io-modes: Wrap shell snippets in literal code blocks Bagas Sanjaya
2025-12-03 1:09 ` [PATCH 3/3] NFSD: nfsd-io-modes: Separate lists Bagas Sanjaya
2025-12-03 6:32 ` [PATCH 0/3] NFSD IO MODES documentation fixes Randy Dunlap
2025-12-03 12:29 ` Jeff Layton
2025-12-03 14:41 ` Chuck Lever
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=20251203010911.14234-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=jlayton@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=snitzer@kernel.org \
--cc=tom@talpey.com \
--cc=trondmy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox