From: Borislav Petkov <bp@alien8.de>
To: Liang Zhou <lullaby2005@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
hpa@zytor.com, corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, zhoul110@chinatelecom.cn
Subject: Re: [PATCH] docs: fix the invalid vt-d spec location
Date: Sun, 18 Apr 2021 18:59:53 +0200 [thread overview]
Message-ID: <20210418165953.GA1206@zn.tnic> (raw)
In-Reply-To: <1618763386-29562-1-git-send-email-zhoul110@chinatelecom.cn>
On Sun, Apr 18, 2021 at 09:29:46AM -0700, Liang Zhou wrote:
> This patch fixes the invalid vt-d spec location.
Avoid having "This patch" or "This commit" in the commit message. It is
tautologically useless.
Also, do
$ git grep 'This patch' Documentation/process
for more details.
> Signed-off-by: Liang Zhou <zhoul110@chinatelecom.cn>
> ---
> Documentation/x86/intel-iommu.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/x86/intel-iommu.rst b/Documentation/x86/intel-iommu.rst
> index 099f13d..e95ee34 100644
> --- a/Documentation/x86/intel-iommu.rst
> +++ b/Documentation/x86/intel-iommu.rst
> @@ -4,7 +4,7 @@ Linux IOMMU Support
>
> The architecture spec can be obtained from the below location.
>
> -http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/vt-directed-io-spec.pdf
> +https://software.intel.com/content/dam/develop/external/us/en/documents-tps/vt-directed-io-spec.pdf
Those links are never stable.
Please open a bugzilla at bugzilla.kernel.org, upload that document
there, like this, for example:
https://bugzilla.kernel.org/show_bug.cgi?id=206537
and then add the *bugzilla* link to intel-iommu.rst so that it doesn't
get invalid again.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-04-18 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 16:29 [PATCH] docs: fix the invalid vt-d spec location Liang Zhou
2021-04-18 16:59 ` Borislav Petkov [this message]
2021-04-19 8:05 ` Steven Zhou
2021-04-20 18:58 ` Borislav Petkov
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=20210418165953.GA1206@zn.tnic \
--to=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lullaby2005@gmail.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhoul110@chinatelecom.cn \
/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