From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux bcachefs <linux-bcachefs@vger.kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Joshua Ashton <joshua@froggi.es>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/4] bcachefs: casefolding.rst fixes
Date: Sat, 22 Feb 2025 16:18:49 +0700 [thread overview]
Message-ID: <20250222091853.16487-1-bagasdotme@gmail.com> (raw)
Hi Kent, hi Joshua,
Here are fixes for casefolding docs. Patches [1/4], [2/4], and [4/4]
fixes htmldocs warnings reported in linux-next.
Enjoy!
Bagas Sanjaya (4):
Documentation: bcachefs: casefolding: Do not italicize NUL
Documentation: bcachefs: casefolding: Fix dentry/dcache considerations
section
Documentation: bcachefs: casefolding: Use bullet list for dirent
structure
Documentation: bcachefs: Add casefolding toctree entry
Documentation/filesystems/bcachefs/casefolding.rst | 13 ++++++++-----
Documentation/filesystems/bcachefs/index.rst | 1 +
2 files changed, 9 insertions(+), 5 deletions(-)
base-commit: 77308424ba26e1b41a7db5d4eae121841a707c05
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-02-22 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 9:18 Bagas Sanjaya [this message]
2025-02-22 9:18 ` [PATCH 1/4] Documentation: bcachefs: casefolding: Do not italicize NUL Bagas Sanjaya
2025-02-22 9:18 ` [PATCH 2/4] Documentation: bcachefs: casefolding: Fix dentry/dcache considerations section Bagas Sanjaya
2025-02-22 9:18 ` [PATCH 3/4] Documentation: bcachefs: casefolding: Use bullet list for dirent structure Bagas Sanjaya
2025-02-22 9:18 ` [PATCH 4/4] Documentation: bcachefs: Add casefolding toctree entry Bagas Sanjaya
2025-02-22 14:07 ` [PATCH 0/4] bcachefs: casefolding.rst fixes Kent Overstreet
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=20250222091853.16487-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=joshua@froggi.es \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox