On Sun, Aug 10, 2025 at 04:16:48PM +0530, Gopi Krishna Menon wrote: > Specifically, fix spelling mistake of "hierarchy" > > Signed-off-by: Gopi Krishna Menon <[email protected]>
Applied > --- > 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.43.0 >
