* [PATCH 1/3] Documentation: bcachefs: Split index toctree
2025-02-24 12:40 [PATCH 0/3] bcachefs: docs index refactoring Bagas Sanjaya
@ 2025-02-24 12:40 ` Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 2/3] Documentation: bcachefs: SubmittingPatches: Demote section headings Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 3/3] Documentation: bcachefs: SubmittingPatches: Convert footnotes to reST syntax Bagas Sanjaya
2 siblings, 0 replies; 4+ messages in thread
From: Bagas Sanjaya @ 2025-02-24 12:40 UTC (permalink / raw)
To: Linux Kernel Mailing List, Linux Documentation, Linux bcachefs
Cc: Kent Overstreet, Jonathan Corbet, Wei Liu, Easwar Hariharan,
Michael Kelley, Purva Yeshi, Bagas Sanjaya
bcachefs subsystem currently has 4 docs: two are development notes and
the rest are actual filesystem docs. These two groups are clearly
distinct and can be organized.
Split the toctree into two, one for each docs group. While at it, also
reduce :maxdepth: so that only title headings are listed in the
toctrees.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/bcachefs/index.rst | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/Documentation/filesystems/bcachefs/index.rst b/Documentation/filesystems/bcachefs/index.rst
index 0415b5d781920d..3864d0ae89c10b 100644
--- a/Documentation/filesystems/bcachefs/index.rst
+++ b/Documentation/filesystems/bcachefs/index.rst
@@ -4,11 +4,28 @@
bcachefs Documentation
======================
+Subsystem-specific development process notes
+--------------------------------------------
+
+Development notes specific to bcachefs. These are intended to supplement
+:doc:`general kernel development handbook </process/index>`.
+
.. toctree::
- :maxdepth: 2
+ :maxdepth: 1
:numbered:
CodingStyle
SubmittingPatches
+
+Filesystem implementation
+-------------------------
+
+Documentation for filesystem features and their implementation details.
+At this moment, only a few of these are described here.
+
+.. toctree::
+ :maxdepth: 1
+ :numbered:
+
casefolding
errorcodes
--
An old man doll... just what I always wanted! - Clara
^ permalink raw reply [flat|nested] 4+ messages in thread* [PATCH 2/3] Documentation: bcachefs: SubmittingPatches: Demote section headings
2025-02-24 12:40 [PATCH 0/3] bcachefs: docs index refactoring Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 1/3] Documentation: bcachefs: Split index toctree Bagas Sanjaya
@ 2025-02-24 12:40 ` Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 3/3] Documentation: bcachefs: SubmittingPatches: Convert footnotes to reST syntax Bagas Sanjaya
2 siblings, 0 replies; 4+ messages in thread
From: Bagas Sanjaya @ 2025-02-24 12:40 UTC (permalink / raw)
To: Linux Kernel Mailing List, Linux Documentation, Linux bcachefs
Cc: Kent Overstreet, Jonathan Corbet, Wei Liu, Easwar Hariharan,
Michael Kelley, Purva Yeshi, Bagas Sanjaya
SubmttingPatches.rst has 4 section headings, all under the same heading
levels. In absence of title headings, these section headings are all
ended up as title headings in the docs output, which also affect
the index toctree (increasing titles to 6 from the original 2)
due to :numbered: option.
Demote second-to-last section headings, making "Submitting patches
to bcachefs" as title heading.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
.../bcachefs/SubmittingPatches.rst | 21 ++++++++++++-------
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/Documentation/filesystems/bcachefs/SubmittingPatches.rst b/Documentation/filesystems/bcachefs/SubmittingPatches.rst
index 026b12ae0d6a20..ece0e85d259807 100644
--- a/Documentation/filesystems/bcachefs/SubmittingPatches.rst
+++ b/Documentation/filesystems/bcachefs/SubmittingPatches.rst
@@ -1,5 +1,10 @@
-Submitting patches to bcachefs:
-===============================
+Submitting patches to bcachefs
+==============================
+
+Here are suggestions for submitting patches to bcachefs subsystem.
+
+Submission checklist
+--------------------
Patches must be tested before being submitted, either with the xfstests suite
[0], or the full bcachefs test suite in ktest [1], depending on what's being
@@ -26,8 +31,8 @@ considered out of date), but try not to deviate too much without reason.
Focus on writing code that reads well and is organized well; code should be
aesthetically pleasing.
-CI:
-===
+CI
+--
Instead of running your tests locally, when running the full test suite it's
prefereable to let a server farm do it in parallel, and then have the results
@@ -39,8 +44,8 @@ a big tech company, you'll need to help out with server costs to get access -
but the CI is not restricted to running bcachefs tests: it runs any ktest test
(which generally makes it easy to wrap other tests that can run in qemu).
-Other things to think about:
-============================
+Other things to think about
+---------------------------
- How will we debug this code? Is there sufficient introspection to diagnose
when something starts acting wonky on a user machine?
@@ -79,8 +84,8 @@ Other things to think about:
tested? (Automated tests exists but aren't in the CI, due to the hassle of
disk image management; coordinate to have them run.)
-Mailing list, IRC:
-==================
+Mailing list, IRC
+-----------------
Patches should hit the list [3], but much discussion and code review happens on
IRC as well [4]; many people appreciate the more conversational approach and
--
An old man doll... just what I always wanted! - Clara
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH 3/3] Documentation: bcachefs: SubmittingPatches: Convert footnotes to reST syntax
2025-02-24 12:40 [PATCH 0/3] bcachefs: docs index refactoring Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 1/3] Documentation: bcachefs: Split index toctree Bagas Sanjaya
2025-02-24 12:40 ` [PATCH 2/3] Documentation: bcachefs: SubmittingPatches: Demote section headings Bagas Sanjaya
@ 2025-02-24 12:40 ` Bagas Sanjaya
2 siblings, 0 replies; 4+ messages in thread
From: Bagas Sanjaya @ 2025-02-24 12:40 UTC (permalink / raw)
To: Linux Kernel Mailing List, Linux Documentation, Linux bcachefs
Cc: Kent Overstreet, Jonathan Corbet, Wei Liu, Easwar Hariharan,
Michael Kelley, Purva Yeshi, Bagas Sanjaya
Footnotes list are outputted in htmldocs simply as long-running
paragraph instead. Use reST numbered footnotes syntax for the job.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
.../bcachefs/SubmittingPatches.rst | 22 ++++++++++---------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/Documentation/filesystems/bcachefs/SubmittingPatches.rst b/Documentation/filesystems/bcachefs/SubmittingPatches.rst
index ece0e85d259807..a455f9cfd15c79 100644
--- a/Documentation/filesystems/bcachefs/SubmittingPatches.rst
+++ b/Documentation/filesystems/bcachefs/SubmittingPatches.rst
@@ -7,7 +7,7 @@ Submission checklist
--------------------
Patches must be tested before being submitted, either with the xfstests suite
-[0], or the full bcachefs test suite in ktest [1], depending on what's being
+[0]_, or the full bcachefs test suite in ktest [1]_, depending on what's being
touched. Note that ktest wraps xfstests and will be an easier method to running
it for most users; it includes single-command wrappers for all the mainstream
in-kernel local filesystems.
@@ -39,7 +39,7 @@ prefereable to let a server farm do it in parallel, and then have the results
in a nice test dashboard (which can tell you which failures are new, and
presents results in a git log view, avoiding the need for most bisecting).
-That exists [2], and community members may request an account. If you work for
+That exists [2]_, and community members may request an account. If you work for
a big tech company, you'll need to help out with server costs to get access -
but the CI is not restricted to running bcachefs tests: it runs any ktest test
(which generally makes it easy to wrap other tests that can run in qemu).
@@ -87,17 +87,19 @@ Other things to think about
Mailing list, IRC
-----------------
-Patches should hit the list [3], but much discussion and code review happens on
-IRC as well [4]; many people appreciate the more conversational approach and
-quicker feedback.
+Patches should hit the list [3]_, but much discussion and code review happens
+on IRC as well [4]_; many people appreciate the more conversational approach
+and quicker feedback.
Additionally, we have a lively user community doing excellent QA work, which
exists primarily on IRC. Please make use of that resource; user feedback is
important for any nontrivial feature, and documenting it in commit messages
would be a good idea.
-[0]: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
-[1]: https://evilpiepirate.org/git/ktest.git/
-[2]: https://evilpiepirate.org/~testdashboard/ci/
-[3]: linux-bcachefs@vger.kernel.org
-[4]: irc.oftc.net#bcache, #bcachefs-dev
+.. rubric:: References
+
+.. [0] git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
+.. [1] https://evilpiepirate.org/git/ktest.git/
+.. [2] https://evilpiepirate.org/~testdashboard/ci/
+.. [3] linux-bcachefs@vger.kernel.org
+.. [4] irc.oftc.net#bcache, #bcachefs-dev
--
An old man doll... just what I always wanted! - Clara
^ permalink raw reply [flat|nested] 4+ messages in thread