From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arch@vger.kernel.org, Yury Khrustalev <yury.khrustalev@arm.com>
Cc: Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Sandipan Das <sandipan@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, x86@kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
nd@arm.com
Subject: Re: [RESEND v4 0/3] mm/pkey: Add PKEY_UNRESTRICTED macro
Date: Mon, 17 Feb 2025 21:33:10 +0000 [thread overview]
Message-ID: <173982794521.4020985.15838989967891150260.b4-ty@arm.com> (raw)
In-Reply-To: <20250113170619.484698-1-yury.khrustalev@arm.com>
On Mon, 13 Jan 2025 17:06:16 +0000, Yury Khrustalev wrote:
> Add PKEY_UNRESTRICTED macro to mman.h and use it in selftests.
>
> For context, this change will also allow for more consistent update of the
> Glibc manual which in turn will help with introducing memory protection
> keys on AArch64 targets.
>
> Applies to 5bc55a333a2f (tag: v6.13-rc7).
>
> [...]
Applied to arm64 (for-next/pkey_unrestricted), thanks!
[1/3] mm/pkey: Add PKEY_UNRESTRICTED macro
https://git.kernel.org/arm64/c/6d61527d931b
[2/3] selftests/mm: Use PKEY_UNRESTRICTED macro
https://git.kernel.org/arm64/c/3809cefe93f6
[3/3] selftests/powerpc: Use PKEY_UNRESTRICTED macro
https://git.kernel.org/arm64/c/00894c3fc917
--
Catalin
next prev parent reply other threads:[~2025-02-17 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 17:06 Yury Khrustalev
2025-01-13 17:06 ` [RESEND v4 1/3] " Yury Khrustalev
2025-01-13 17:06 ` [RESEND v4 2/3] selftests/mm: Use " Yury Khrustalev
2025-01-13 17:06 ` [RESEND v4 3/3] selftests/powerpc: " Yury Khrustalev
2025-02-12 17:24 ` [RESEND v4 0/3] mm/pkey: Add " Catalin Marinas
2025-02-12 21:29 ` Andrew Morton
2025-02-17 21:33 ` Catalin Marinas [this message]
2025-02-18 9:56 ` Yury Khrustalev
-- strict thread matches above, loose matches on Subject: below --
2024-12-09 9:47 Yury Khrustalev
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=173982794521.4020985.15838989967891150260.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dave.hansen@linux.intel.com \
--cc=joey.gouly@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nd@arm.com \
--cc=sandipan@linux.ibm.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yury.khrustalev@arm.com \
/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