From: Borislav Petkov <bp@alien8.de>
To: Richard Lyu <richard.lyu@suse.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/x86: Update AMD IOMMU specification locationi
Date: Mon, 5 Jan 2026 16:19:59 +0100 [thread overview]
Message-ID: <20260105151959.GAaVvWnyEonFSjilB_@fat_crate.local> (raw)
In-Reply-To: <20260105150548.73422-1-richard.lyu@suse.com>
On Mon, Jan 05, 2026 at 11:05:54PM +0800, Richard Lyu wrote:
> The current link to the AMD I/O Virtualization Technology IOMMU
> specification (document 48882) in Documentation/arch/x86/iommu.rst
> is outdated and points to a defunct URL on the AMD website.
>
> Update the link in Documentation/arch/x86/iommu.rst to the current stable
> location for the specification. This ensures users can easily access the
> required architectural details.
>
> Signed-off-by: Richard Lyu <richard.lyu@suse.com>
> ---
> Documentation/arch/x86/iommu.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/arch/x86/iommu.rst b/Documentation/arch/x86/iommu.rst
> index 41fbadfe2221..cd1843812b4b 100644
> --- a/Documentation/arch/x86/iommu.rst
> +++ b/Documentation/arch/x86/iommu.rst
> @@ -5,7 +5,7 @@ x86 IOMMU Support
> The architecture specs can be obtained from the below locations.
>
> - Intel: http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/vt-directed-io-spec.pdf
> -- AMD: https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/specifications/48882_3_07_PUB.pdf
> +- AMD: https://docs.amd.com/v/u/en-US/48882_IOMMU
>
> This guide gives a quick cheat sheet for some basic understanding.
What I'd do instead is leave enough breadcrumbs here in the text - doc ID, doc
title etc, so that people can actually find the document by using a search
engine which has managed to index it.
Instead of updating links mindlessly because those do change constantly. No
matter the vendor - as long as it is a corporate website, links get changed on
a regular basis.
I'd say.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-01-05 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 15:05 [PATCH] docs/x86: Update AMD IOMMU specification locationi Richard Lyu
2026-01-05 15:19 ` Borislav Petkov [this message]
[not found] ` <CANC36oUVpEF1r3JK8Po6a4RwxRQ4qGMLvmWzxn-Zf=W2tF9-eQ@mail.gmail.com>
2026-01-07 14:53 ` Borislav Petkov
2026-01-08 9:36 ` Richard Lyu
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=20260105151959.GAaVvWnyEonFSjilB_@fat_crate.local \
--to=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=richard.lyu@suse.com \
--cc=tglx@linutronix.de \
--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