Re: [PATCH] clocksource/drivers/arm_arch_timer: Fix event stream param in Kconfig
From: Marc Zyngier
Date: Tue Oct 25 2022 - 06:27:17 EST
Hi Tyler,
On Mon, 24 Oct 2022 20:51:18 +0100,
Tyler Hicks <code@xxxxxxxxxxx> wrote:
>
> From: "Tyler Hicks (Microsoft)" <code@xxxxxxxxxxx>
>
> Fix the event stream timer command line parameter name that's documented
> in the Kconfig description for CONFIG_ARM_ARCH_TIMER_EVTSTREAM. It
> didn't match the command line parameter name that's actually honored in
> the source code.
>
> Reported-by: Vijay Balakrishna <vijayb@xxxxxxxxxxxxxxxxxxx>
> Fixes: 46fd5c6b3059 ("clocksource/drivers/arm_arch_timer: Control the evtstrm via the cmdline")
> Cc: stable@xxxxxxxxxxxxxxx
No, this really doesn't deserve a Cc: stable. This bit may be wrong,
but we have the correct information in the kernel-parameters.txt file,
which is authoritative AFAIC.
> Signed-off-by: Tyler Hicks (Microsoft) <code@xxxxxxxxxxx>
> ---
> drivers/clocksource/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> index 4469e7f555e9..dcc274460973 100644
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> @@ -315,7 +315,7 @@ config ARM_ARCH_TIMER_EVTSTREAM
> executing the wfe instruction at a frequency represented as a
> power-of-2 divisor of the clock rate. The behaviour can also be
> overridden on the command line using the
> - clocksource.arm_arch_timer.evtstream parameter.
> + clocksource.arm_arch_timer.evtstrm parameter.
> The main use of the event stream is wfe-based timeouts of userspace
> locking implementations. It might also be useful for imposing timeout
> on wfe to safeguard against any programming errors in case an expected
With this tag dropped,
Acked-by: Marc Zyngier <maz@xxxxxxxxxx>
M.
--
Without deviation from the norm, progress is not possible.