diff options
| author | Andrew Sayers <[email protected]> | 2025-04-11 15:25:04 +0000 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2025-04-22 11:58:30 +0000 |
| commit | 036c94c9fd05824f86a92db115eba2773cc79231 (patch) | |
| tree | 28f06cd406a8f9edf388b357538895b35e60e37e /rust/helpers/helpers.c | |
| parent | PM: sleep: Make suspend of devices more asynchronous (diff) | |
| download | kernel-036c94c9fd05824f86a92db115eba2773cc79231.tar.gz kernel-036c94c9fd05824f86a92db115eba2773cc79231.zip | |
PM: sleep: Use two lines for "Restarting..." / "done" messages
Other messages are occasionally printed between these two, for example:
[203104.106534] Restarting tasks ...
[203104.106559] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[203104.112354] done.
This seems to be a timing issue, seen in two of the eleven
hibernation exits in my current `dmesg` output.
When printed on its own, the "done" message has the default log level.
This makes the output of `dmesg --level=warn` quite misleading.
Add enough context for the "done" messages to make sense on their own,
and use the same log level for all messages.
Change the messages to "<event>..." / "Done <event>.", unlike a449dfbfc089
which uses "<event>..." / "<event> completed.". Front-loading the unique
part of the message makes it easier to scan the log, and reduces ambiguity
for users who aren't confident in their English comprehension.
Reviewed-by: Lucas De Marchi <[email protected]>
Signed-off-by: Andrew Sayers <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'rust/helpers/helpers.c')
0 files changed, 0 insertions, 0 deletions