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>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH] Documentation: bcachefs: Add explicit title for idle work design doc
Date: Wed, 20 Aug 2025 07:22:18 +0700 [thread overview]
Message-ID: <20250820002218.11547-1-bagasdotme@gmail.com> (raw)
Commit 9e260e4590e044 ("docs: bcachefs: idle work scheduling design doc")
adds design doc (desiderata) for idle work scheduling, but missed
explicit title, causing its two section headings to be toctree entries
instead.
Add the title.
Fixes: 9e260e4590e0 ("docs: bcachefs: idle work scheduling design doc")
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/bcachefs/future/idle_work.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/filesystems/bcachefs/future/idle_work.rst b/Documentation/filesystems/bcachefs/future/idle_work.rst
index 59a332509dcd97..30f2844c3d9e5e 100644
--- a/Documentation/filesystems/bcachefs/future/idle_work.rst
+++ b/Documentation/filesystems/bcachefs/future/idle_work.rst
@@ -1,4 +1,5 @@
-Idle/background work classes design doc:
+Idle/background work classes desiderata
+=======================================
Right now, our behaviour at idle isn't ideal, it was designed for servers that
would be under sustained load, to keep pending work at a "medium" level, to
base-commit: 37c52167b007d9d0bb8c5ed53dd6efc4969a1356
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-08-20 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 0:22 Bagas Sanjaya [this message]
2025-08-20 1:08 ` [PATCH] Documentation: bcachefs: Add explicit title for idle work design doc Kent Overstreet
2025-08-20 2:29 ` Bagas Sanjaya
2025-08-20 2:31 ` Kent Overstreet
2025-08-20 3:11 ` Bagas Sanjaya
2025-08-20 1:18 ` Randy Dunlap
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=20250820002218.11547-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--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