diff options
| author | Waiman Long <longman@redhat.com> | 2025-01-24 20:54:41 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-02-21 14:01:38 +0100 |
| commit | ebf0ac02e2d8e9f9580bc162d09b0c34ead0efc3 (patch) | |
| tree | b554c651c5a3151dc3d38f4cc8239f178f778c77 /kernel/fail_function.c | |
| parent | 5ab11a4e219e93b8b31a27f8ec98d42afadd8b7a (diff) | |
| download | linux-ebf0ac02e2d8e9f9580bc162d09b0c34ead0efc3.tar.gz linux-ebf0ac02e2d8e9f9580bc162d09b0c34ead0efc3.tar.bz2 linux-ebf0ac02e2d8e9f9580bc162d09b0c34ead0efc3.zip | |
clocksource: Use pr_info() for "Checking clocksource synchronization" message
[ Upstream commit 1f566840a82982141f94086061927a90e79440e5 ]
The "Checking clocksource synchronization" message is normally printed
when clocksource_verify_percpu() is called for a given clocksource if
both the CLOCK_SOURCE_UNSTABLE and CLOCK_SOURCE_VERIFY_PERCPU flags
are set.
It is an informational message and so pr_info() is the correct choice.
Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
Acked-by: John Stultz <jstultz@google.com>
Link: https://lore.kernel.org/all/20250125015442.3740588-1-longman@redhat.com
Stable-dep-of: 6bb05a33337b ("clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context")
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'kernel/fail_function.c')
0 files changed, 0 insertions, 0 deletions