* [PATCH v2] Documentation: bcachefs: Add explicit title for idle work design doc
@ 2025-08-21 0:46 Bagas Sanjaya
2025-08-21 3:00 ` Randy Dunlap
2025-08-21 16:09 ` Kent Overstreet
0 siblings, 2 replies; 3+ messages in thread
From: Bagas Sanjaya @ 2025-08-21 0:46 UTC (permalink / raw)
To: Linux Kernel Mailing List, Linux Documentation, Linux bcachefs
Cc: Kent Overstreet, Jonathan Corbet, Randy Dunlap, Bagas Sanjaya
Commit 9e260e4590e044 ("docs: bcachefs: idle work scheduling design
doc") adds design doc for idle work scheduling, but misses explicit
title heading, 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>
---
Changes since v1 [1]:
* Keep original "design doc" title (Kent)
[1]: https://lore.kernel.org/linux-doc/20250820002218.11547-1-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..8519fdcaa5ff49 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 design doc
+=======================================
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2] Documentation: bcachefs: Add explicit title for idle work design doc
2025-08-21 0:46 [PATCH v2] Documentation: bcachefs: Add explicit title for idle work design doc Bagas Sanjaya
@ 2025-08-21 3:00 ` Randy Dunlap
2025-08-21 16:09 ` Kent Overstreet
1 sibling, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2025-08-21 3:00 UTC (permalink / raw)
To: Bagas Sanjaya, Linux Kernel Mailing List, Linux Documentation,
Linux bcachefs
Cc: Kent Overstreet, Jonathan Corbet
On 8/20/25 5:46 PM, Bagas Sanjaya wrote:
> Commit 9e260e4590e044 ("docs: bcachefs: idle work scheduling design
> doc") adds design doc for idle work scheduling, but misses explicit
> title heading, 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>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Changes since v1 [1]:
>
> * Keep original "design doc" title (Kent)
>
> [1]: https://lore.kernel.org/linux-doc/20250820002218.11547-1-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..8519fdcaa5ff49 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 design doc
> +=======================================
>
> 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
--
~Randy
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] Documentation: bcachefs: Add explicit title for idle work design doc
2025-08-21 0:46 [PATCH v2] Documentation: bcachefs: Add explicit title for idle work design doc Bagas Sanjaya
2025-08-21 3:00 ` Randy Dunlap
@ 2025-08-21 16:09 ` Kent Overstreet
1 sibling, 0 replies; 3+ messages in thread
From: Kent Overstreet @ 2025-08-21 16:09 UTC (permalink / raw)
To: Bagas Sanjaya
Cc: Linux Kernel Mailing List, Linux Documentation, Linux bcachefs,
Jonathan Corbet, Randy Dunlap
On Thu, Aug 21, 2025 at 07:46:21AM +0700, Bagas Sanjaya wrote:
> Commit 9e260e4590e044 ("docs: bcachefs: idle work scheduling design
> doc") adds design doc for idle work scheduling, but misses explicit
> title heading, 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>
Applied
> ---
> Changes since v1 [1]:
>
> * Keep original "design doc" title (Kent)
>
> [1]: https://lore.kernel.org/linux-doc/20250820002218.11547-1-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..8519fdcaa5ff49 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 design doc
> +=======================================
>
> 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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-08-21 16:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-21 0:46 [PATCH v2] Documentation: bcachefs: Add explicit title for idle work design doc Bagas Sanjaya
2025-08-21 3:00 ` Randy Dunlap
2025-08-21 16:09 ` Kent Overstreet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).