From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Cc: kvm-ppc@vger.kernel.org, linux-api@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/3] remove PROT_SAO support and disable
Date: Fri, 24 Jul 2020 23:25:11 +1000 (AEST) [thread overview]
Message-ID: <159559696901.1657499.15799900734438878764.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20200703011958.1166620-1-npiggin@gmail.com>
On Fri, 3 Jul 2020 11:19:55 +1000, Nicholas Piggin wrote:
> It was suggested that I post this to a wider audience on account of
> the change to supported userspace features in patch 2 particularly.
>
> Thanks,
> Nick
>
> Nicholas Piggin (3):
> powerpc: remove stale calc_vm_prot_bits comment
> powerpc/64s: remove PROT_SAO support
> powerpc/64s/hash: disable subpage_prot syscall by default
>
> [...]
Applied to powerpc/next.
[1/3] powerpc: Remove stale calc_vm_prot_bits() comment
https://git.kernel.org/powerpc/c/f4ac1774f2cba44994ce9ac0a65772e4656ac2df
[2/3] powerpc/64s: Remove PROT_SAO support
https://git.kernel.org/powerpc/c/5c9fa16e8abd342ce04dc830c1ebb2a03abf6c05
[3/3] powerpc/64s/hash: Disable subpage_prot syscall by default
https://git.kernel.org/powerpc/c/63396ada804c676e070bd1b8663046f18698ab27
cheers
prev parent reply other threads:[~2020-07-24 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 1:19 Nicholas Piggin
2020-07-03 1:19 ` [PATCH v2 1/3] powerpc: remove stale calc_vm_prot_bits comment Nicholas Piggin
2020-07-03 1:19 ` [PATCH v2 2/3] powerpc/64s: remove PROT_SAO support Nicholas Piggin
2020-07-09 4:34 ` Paul Mackerras
2020-07-09 10:20 ` Nicholas Piggin
2020-07-03 1:19 ` [PATCH v2 3/3] powerpc/64s/hash: disable subpage_prot syscall by default Nicholas Piggin
2020-07-24 13:25 ` 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=159559696901.1657499.15799900734438878764.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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