[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANDhNCr-3Pe2Cp9gjHLw1o=OHfPr0X7H+L6_rdGXQ-1pwc0+JA@mail.gmail.com>
Date: Fri, 24 Jan 2025 11:24:36 -0800
From: John Stultz <jstultz@...gle.com>
To: Waiman Long <longman@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Stephen Boyd <sboyd@...nel.org>,
Feng Tang <feng.tang@...el.com>, "Paul E. McKenney" <paulmck@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Clark Williams <clrkwllms@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
linux-rt-devel@...ts.linux.dev
Subject: Re: [PATCH 1/2] clocksource: Use pr_info() for "Checking clocksource
synchronization" message
On Fri, Jan 24, 2025 at 10:59 AM Waiman Long <longman@...hat.com> wrote:
>
> 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() should be used
> instead of pr_warn().
>
> Signed-off-by: Waiman Long <longman@...hat.com>
Acked-by: John Stultz <jstultz@...gle.com>
Thanks for sending this!
-john
Powered by blists - more mailing lists