From: Mario Limonciello <mario.limonciello@amd.com>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: [PATCH] Documentation: amd-debugging: update amd-debug-tools URL
Date: Wed, 18 Nov 2026 12:16:40 -0600 [thread overview]
Message-ID: <20261118-superm1-amd-debug-tools-url-v1-1-102516e88a0a@amd.com> (raw)
The amd-debug-tools project has moved development from git.kernel.org
to GitHub so that it can take advantage of forge flows that don't
exist at git.kernel.org.
* pull requests
* CI
* automated PyPi releases
Update the link in the s2idle debugging tool section to point at the new
location.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
Documentation/arch/x86/amd-debugging.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/arch/x86/amd-debugging.rst b/Documentation/arch/x86/amd-debugging.rst
index 3176a1240feeb..f5f1e02131882 100644
--- a/Documentation/arch/x86/amd-debugging.rst
+++ b/Documentation/arch/x86/amd-debugging.rst
@@ -42,7 +42,7 @@ s2idle debugging tool
As there are a lot of places that problems can occur, a debugging tool has been
created at
-`amd-debug-tools <https://git.kernel.org/pub/scm/linux/kernel/git/superm1/amd-debug-tools.git/about/>`_
+`amd-debug-tools <https://github.com/rocm/amd-debug-tools>`_
that can help test for common problems and offer suggestions.
If you have an s2idle issue, it's best to start with this and follow instructions
---
base-commit: 4405c18c95d2d0f99f6c581ef0ee8591a1aa6ccd
change-id: 20261118-superm1-amd-debug-tools-url-0ce547e55d40
Best regards,
--
Mario Limonciello <mario.limonciello@amd.com>
reply other threads:[~2026-11-18 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261118-superm1-amd-debug-tools-url-v1-1-102516e88a0a@amd.com \
--to=mario.limonciello@amd.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®