From: Sahil <chandna.linuxkernel@gmail.com>
To: kent.overstreet@linux.dev, corbet@lwn.net, rdunlap@infradead.org,
linux-bcachefs@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] docs: bcachefs: fix typo in idle_work documentation
Date: Sat, 23 Aug 2025 17:05:33 +0530 [thread overview]
Message-ID: <c9cbd06a-9564-452b-bf05-8bfa83b81aa2@gmail.com> (raw)
In-Reply-To: <20250822223416.23345-1-chandna.linuxkernel@gmail.com>
Fix minor spelling mistake in idle_work:
- heirarchy -> hierarchy
Changes in v2:
- Dropped cgroup, idle changes (already being fixed)
- Dropped xfs changes (already fixed)
- Only keep bcachefs doc fix
Link:
https://lore.kernel.org/linux-doc/23de3jgp44vih5g6hjgc2ji6momi5t3w7rfkm5mgtajicbbg7a@7r5hgt5e7eir/
Based on v6.17-rc2.
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Sahil Chandna <chandna.linuxkernel@gmail.com>
---
Documentation/filesystems/bcachefs/future/idle_work.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/bcachefs/future/idle_work.rst
b/Documentation/filesystems/bcachefs/future/idle_work.rst
index 59a332509dcd..f1202113dde0 100644
--- a/Documentation/filesystems/bcachefs/future/idle_work.rst
+++ b/Documentation/filesystems/bcachefs/future/idle_work.rst
@@ -11,10 +11,10 @@ idle" so the system can go to sleep. We don't want
to be dribbling out
background work while the system should be idle.
The complicating factor is that there are a number of background tasks,
which
-form a heirarchy (or a digraph, depending on how you divide it up) - one
+form a hierarchy (or a digraph, depending on how you divide it up) - one
background task may generate work for another.
-Thus proper idle detection needs to model this heirarchy.
+Thus proper idle detection needs to model this hierarchy.
- Foreground writes
- Page cache writeback
@@ -51,7 +51,7 @@ IDLE REGIME
When the system becomes idle, we should start flushing our pending work
quicker so the system can go to sleep.
-Note that the definition of "idle" depends on where in the heirarchy a task
+Note that the definition of "idle" depends on where in the hierarchy a task
is - a task should start flushing work more quickly when the task above
it has
stopped generating new work.
--
2.34.1
next parent reply other threads:[~2025-08-23 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250822223416.23345-1-chandna.linuxkernel@gmail.com>
2025-08-23 11:35 ` Sahil [this message]
2025-08-23 16:08 ` [PATCH v2] docs: bcachefs: fix typo in idle_work documentation Kent Overstreet
[not found] <1055aa42-248a-4d14-8ae6-dc97878e33e7@gmail.com>
2025-08-26 5:05 ` Sahil
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=c9cbd06a-9564-452b-bf05-8bfa83b81aa2@gmail.com \
--to=chandna.linuxkernel@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 \
--cc=rdunlap@infradead.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