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 v2] Documentation: amd-debugging: update amd-debug-tools URL
Date: Thu, 19 Nov 2026 12:35:47 -0600 [thread overview]
Message-ID: <20261119-master-v2-1-00c5a7d76ef1@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>
---
Changes in v2:
- Correct second location (Sashiko, Dave)
- Link to v1: https://patch.msgid.link/20261118-superm1-amd-debug-tools-url-v1-1-102516e88a0a@amd.com
---
Documentation/arch/x86/amd-debugging.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/arch/x86/amd-debugging.rst b/Documentation/arch/x86/amd-debugging.rst
index 3176a1240feeb..6ebb3c862dd3f 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
@@ -321,7 +321,7 @@ Tool assisted Parsing
---------------------
As mentioned above, parsing by hand can be tedious, especially with a lot of
messages. To help with this, a 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>`_
to help parse the messages.
Random reboot issues
---
base-commit: 8dac6df92a2e66e2098bbc69061964cfe7e8375b
change-id: 20261119-master-87aeaeae142b
Best regards,
--
Mario Limonciello <mario.limonciello@amd.com>
reply other threads:[~2026-11-19 18:36 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=20261119-master-v2-1-00c5a7d76ef1@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®