From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Daniel Tang <danielzgtg.opensource@gmail.com>, linux-doc@vger.kernel.org
Cc: 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>, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v2 RESEND] Documentation/protection-keys: Mark as available on AMD
Date: Thu, 15 Jan 2026 16:43:04 +0700 [thread overview]
Message-ID: <aWi2qBOg8ApOzbW-@archie.me> (raw)
In-Reply-To: <45127739.pHGDlbCDJk@daniel-desktop3>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Wed, Jan 14, 2026 at 09:06:20PM -0500, Daniel Tang wrote:
> diff --git a/Documentation/core-api/protection-keys.rst b/Documentation/core-api/protection-keys.rst
> index 7eb7c6023e09..59e7c178af4b 100644
> --- a/Documentation/core-api/protection-keys.rst
> +++ b/Documentation/core-api/protection-keys.rst
> @@ -11,7 +11,7 @@ application changes protection domains.
> Pkeys Userspace (PKU) is a feature which can be found on:
> * Intel server CPUs, Skylake and later
> * Intel client CPUs, Tiger Lake (11th Gen Core) and later
> - * Future AMD CPUs
> + * AMD Zen 3 and later
> * arm64 CPUs implementing the Permission Overlay Extension (FEAT_S1POE)
>
> x86_64
Acked-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-01-15 9:43 UTC|newest]
Thread overview: 6+ 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
2026-01-15 2:06 ` [PATCH v2 RESEND] " Daniel Tang
2026-01-15 9:43 ` Bagas Sanjaya [this message]
2025-11-20 1:08 ` [PATCH] " Daniel Tang
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=aWi2qBOg8ApOzbW-@archie.me \
--to=bagasdotme@gmail.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=danielzgtg.opensource@gmail.com \
--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