| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <c9cbd06a-9564-452b-bf05-8bfa83b81aa2@gmail.com> Date: Sat, 23 Aug 2025 17:05:33 +0530 From: Sahil <chandna.linuxkernel@...il.com> To: kent.overstreet@...ux.dev, corbet@....net, rdunlap@...radead.org, linux-bcachefs@...r.kernel.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: [PATCH v2] docs: bcachefs: fix typo in idle_work documentation 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@...radead.org> Signed-off-by: Sahil Chandna <chandna.linuxkernel@...il.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
Powered by blists - more mailing lists