From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Sandipan Das <sandipan@linux.ibm.com>, mpe@ellerman.id.au
Cc: linuxram@us.ibm.com, ruscur@russell.cc,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
fweimer@redhat.com, bauerman@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, aneesh.kumar@linux.ibm.com
Subject: Re: [PATCH v3 0/3] selftests: powerpc: Fixes and execute-disable test for pkeys
Date: Thu, 16 Jul 2020 22:56:13 +1000 (AEST) [thread overview]
Message-ID: <159490400411.3805857.17323999819214487510.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200604125610.649668-1-sandipan@linux.ibm.com>
On Thu, 4 Jun 2020 18:26:07 +0530, Sandipan Das wrote:
> This fixes the way the Authority Mask Register (AMR) is updated
> by the existing pkey tests and adds a new test to verify the
> functionality of execute-disabled pkeys.
>
> Previous versions can be found at:
> v2: https://lore.kernel.org/linuxppc-dev/20200527030342.13712-1-sandipan@linux.ibm.com/
> v1: https://lore.kernel.org/linuxppc-dev/20200508162332.65316-1-sandipan@linux.ibm.com/
>
> [...]
Applied to powerpc/next.
[1/3] selftests/powerpc: Fix pkey access right updates
https://git.kernel.org/powerpc/c/828ca4320d130bbe1d12866152600c49ff6a9f79
[2/3] selftests/powerpc: Move Hash MMU check to utilities
https://git.kernel.org/powerpc/c/c405b738daf9d8e8a5aedfeb6be851681e65e54b
[3/3] selftests/powerpc: Add test for execute-disabled pkeys
https://git.kernel.org/powerpc/c/1addb6444791f9e87fce0eb9882ec96a4a76e615
cheers
prev parent reply other threads:[~2020-07-16 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 12:56 [PATCH v3 0/3] selftests: powerpc: Fixes and execute-disable test for pkeys Sandipan Das
2020-06-04 12:56 ` [PATCH v3 1/3] selftests: powerpc: Fix pkey access right updates Sandipan Das
2020-06-04 12:56 ` [PATCH v3 2/3] selftests: powerpc: Move Hash MMU check to utilities Sandipan Das
2020-06-04 12:56 ` [PATCH v3 3/3] selftests: powerpc: Add test for execute-disabled pkeys Sandipan Das
2020-07-16 12:56 ` Michael Ellerman [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=159490400411.3805857.17323999819214487510.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bauerman@linux.ibm.com \
--cc=fweimer@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=ruscur@russell.cc \
--cc=sandipan@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).