From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-doc@vger.kernel.org, Haiyue Wang <haiyuewa@163.com>
Cc: Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>,
Carlos Bilbao <carlos.bilbao@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
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>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Akshay Gupta <akshay.gupta@amd.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] docs: fix PPR for AMD EPYC broken link
Date: Mon, 05 Jan 2026 17:28:58 +0200 [thread overview]
Message-ID: <176762693843.2568.9282406819072603735.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20251230133101.14362-1-haiyuewa@163.com>
On Tue, 30 Dec 2025 21:30:50 +0800, Haiyue Wang wrote:
> As 'AMD Documentation Hub' [1] announced: "All technical documentation,
> including for AMD EPYC™ processors ..., and more is now hosted on the
> AMD Technical Information Portal (TIP) [2]".
>
> By searching the No.55898, update the new URL.
>
> [1] https://www.amd.com/en/search/documentation/hub.html
> [2] https://docs.amd.com/
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] docs: fix PPR for AMD EPYC broken link
commit: c92724b40c2f36ca0f2a789cf8cb80dd51107f25
--
i.
prev parent reply other threads:[~2026-01-05 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 13:30 Haiyue Wang
2025-12-30 23:23 ` Bagas Sanjaya
2026-01-05 15:28 ` Ilpo Järvinen [this message]
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=176762693843.2568.9282406819072603735.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=akshay.gupta@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=carlos.bilbao@kernel.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyuewa@163.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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
all inboxes | Powered by JetHome®