From 98f768cd1103d05e42b3cf9acd307ad84866203c Mon Sep 17 00:00:00 2001 From: Marco Crivellari Date: Wed, 2 Sep 2026 11:24:25 +0200 Subject: [PATCH] Documentation/no_hz: Change dynticks-testing repository name Currently the documentation still mention dynticks-testing. Recently the repository name and the tool have been renamed to cpunoise (see Link tag below), so fix the URL. Link: https://lore.kernel.org/all/20260815083728.15470-1-marco.crivellari@suse.com/ Signed-off-by: Marco Crivellari Acked-by: Frederic Weisbecker Signed-off-by: Jonathan Corbet Message-ID: <20260902092434.85096-3-marco.crivellari@suse.com> --- Documentation/timers/no_hz.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/timers/no_hz.rst b/Documentation/timers/no_hz.rst index 7fe8ef9718d8..4006cab64079 100644 --- a/Documentation/timers/no_hz.rst +++ b/Documentation/timers/no_hz.rst @@ -204,9 +204,9 @@ but do not see any change in your workload's behavior. Is this because your workload isn't affected that much by OS jitter, or is it because something else is in the way? This section helps answer this question by providing a simple OS-jitter test suite, which is available on branch -master of the following git archive: +master of the following git repository: -git://git.kernel.org/pub/scm/linux/kernel/git/frederic/dynticks-testing.git +https://git.kernel.org/pub/scm/linux/kernel/git/frederic/cpunoise.git Clone this archive and follow the instructions in the README file. This test procedure will produce a trace that will allow you to evaluate