Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5eb6f9ad authored by Viresh Kumar's avatar Viresh Kumar Committed by Rafael J. Wysocki
Browse files

PM / Documentation: Fix minor issue in freezing_of_tasks.txt 



In a paragraph, "kernel thread" is mistakenly written as "kernel". Fix this by
adding thread after word "kernel".

Changes are shown in multiple lines, as they are realigned to 80 col width.

Signed-off-by: default avatarViresh Kumar <viresh.kumar@st.com>
Acked-by: default avatarPavel Machek <pavel@ucw.cz>
Signed-off-by: default avatarRafael J. Wysocki <rjw@sisk.pl>
parent f581b63a

Documentation/power/freezing-of-tasks.txt

+4 −4
Original line number Original line Diff line number Diff line
@@ -120,10 +120,10 @@ So in practice, the 'at all' may become a 'why freeze kernel threads?' and 
freezing user threads I don't find really objectionable."

freezing user threads I don't find really objectionable."





Still, there are kernel threads that may want to be freezable.  For example, if

Still, there are kernel threads that may want to be freezable.  For example, if

a kernel that belongs to a device driver accesses the device directly, it in

a kernel thread that belongs to a device driver accesses the device directly, it

principle needs to know when the device is suspended, so that it doesn't try to

in principle needs to know when the device is suspended, so that it doesn't try

access it at that time.  However, if the kernel thread is freezable, it will be

to access it at that time.  However, if the kernel thread is freezable, it will

frozen before the driver's .suspend() callback is executed and it will be

be frozen before the driver's .suspend() callback is executed and it will be

thawed after the driver's .resume() callback has run, so it won't be accessing

thawed after the driver's .resume() callback has run, so it won't be accessing

the device while it's suspended.

the device while it's suspended.