From: Daniel Tang <danielzgtg.opensource@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-doc@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Ira Weiny <ira.weiny@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Babu Moger <babu.moger@amd.com>
Subject: Re: [PATCH] Documentation/protection-keys: Mark as available on AMD
Date: Wed, 19 Nov 2025 20:08:32 -0500 [thread overview]
Message-ID: <2169582.ukoFCf946E@daniel-desktop3> (raw)
In-Reply-To: <20251119215038.GHaR47rlpLKZlu-m0y@fat_crate.local>
On Wednesday, 19 November 2025, 16:50:38 EST Borislav Petkov <bp@alien8.de> wrote:
> 55898 for Zen3
Added mention.
> 56176 for Zen2
I was unable to locate that document. AMD's website had redirects, and
linkrot affected wikichip.org and github.com/amd/amd_energy. I'll just
leave it out.
prev parent reply other threads:[~2025-11-20 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 14:01 [PATCH] Documentation/protection-keys: Mark as available on AMD Daniel Tang
2025-11-19 21:50 ` Borislav Petkov
2025-11-20 0:47 ` [PATCH v2] " Daniel Tang
2025-11-20 1:08 ` Daniel Tang [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=2169582.ukoFCf946E@daniel-desktop3 \
--to=danielzgtg.opensource@gmail.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).