From: Yury Khrustalev <yury.khrustalev@arm.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Kevin Brodsky <kevin.brodsky@arm.com>,
<linux-arch@vger.kernel.org>, "Arnd Bergmann" <arnd@arndb.de>,
Joey Gouly <joey.gouly@arm.com>,
Dave Hansen <dave.hansen@linux.intel.com>, <nd@arm.com>
Subject: Re: [PATCH] mm/pkey: Add PKEY_UNRESTRICTED macro
Date: Mon, 28 Oct 2024 08:33:10 +0000 [thread overview]
Message-ID: <Zx9MIsVTKoddY7I6@arm.com> (raw)
In-Reply-To: <dbe74360-dc58-4613-9b95-7a950f69bc9b@intel.com>
Hi,
On Fri, Oct 25, 2024 at 07:48:01AM -0700, Dave Hansen wrote:
> On 10/25/24 01:26, Kevin Brodsky wrote:
> >> It would be much appreciated if someone could make a pass over kernel
> >> code and fix up the places where PKEY_UNRESTRICTED makes things more clear.
> > It doesn't look like kernel code would have a use for it at the moment,
> > but I have found a few places in kselftests (mm, ppc) where 0 could be
> > replaced with PKEY_UNRESTRICTED. I can send a follow-up series.
>
> Just doing it in the selftests would be great.
Thank you for the feedback, I've sent v2 with updated tests [1].
[1] https://lore.kernel.org/linux-arch/20241027170006.464252-1-yury.khrustalev@arm.com/
Kind regards,
Yury
prev parent reply other threads:[~2024-10-28 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 12:01 [PATCH] mm/pkey: Add PKEY_UNRESTRICTED macro Yury Khrustalev
2024-10-22 12:56 ` Kevin Brodsky
2024-10-22 14:04 ` Dave Hansen
2024-10-22 15:11 ` Kevin Brodsky
2024-10-22 17:15 ` Dave Hansen
2024-10-25 8:26 ` Kevin Brodsky
2024-10-25 14:48 ` Dave Hansen
2024-10-28 8:33 ` Yury Khrustalev [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=Zx9MIsVTKoddY7I6@arm.com \
--to=yury.khrustalev@arm.com \
--cc=arnd@arndb.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=joey.gouly@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=nd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.