From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Michal Hocko <mhocko@suse.com>,
Marco Crivellari <marco.crivellari@suse.com>
Subject: [PATCH v3 2/2] Documentation/no_hz: Change dynticks-testing repository name
Date: Wed, 2 Sep 2026 11:24:25 +0200 [thread overview]
Message-ID: <20260902092434.85096-3-marco.crivellari@suse.com> (raw)
In-Reply-To: <20260902092434.85096-1-marco.crivellari@suse.com>
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 <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
--
2.55.0
next prev parent reply other threads:[~2026-09-02 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 9:24 [PATCH v3 0/2] doc: Rename dynticks-testing to cpunoise Marco Crivellari
2026-09-02 9:24 ` [PATCH v3 1/2] doc: Change dynticks-testing repository name Marco Crivellari
2026-09-02 10:42 ` Sebastian Andrzej Siewior
2026-09-02 9:24 ` Marco Crivellari [this message]
2026-09-02 14:02 ` [PATCH v3 0/2] doc: Rename dynticks-testing to cpunoise Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260902092434.85096-3-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=anna-maria@linutronix.de \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox