From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: x86@kernel.org, npiggin@gmail.com, linux-mm@kvack.org,
paulus@samba.org, akpm@linux-foundation.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V4 0/5] NestMMU pte upgrade workaround for mprotect
Date: Wed, 19 Dec 2018 08:48:02 +0530 [thread overview]
Message-ID: <87tvjafbmd.fsf@linux.ibm.com> (raw)
In-Reply-To: <20181218171703.GA22729@infradead.org>
Christoph Hellwig <hch@infradead.org> writes:
> This series seems to miss patches 1 and 2.
https://lore.kernel.org/linuxppc-dev/20181218094137.13732-2-aneesh.kumar@linux.ibm.com/
https://lore.kernel.org/linuxppc-dev/20181218094137.13732-3-aneesh.kumar@linux.ibm.com/
-aneesh
WARNING: multiple messages have this Message-ID (diff)
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: npiggin@gmail.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au, akpm@linux-foundation.org, x86@kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: [PATCH V4 0/5] NestMMU pte upgrade workaround for mprotect
Date: Wed, 19 Dec 2018 08:48:02 +0530 [thread overview]
Message-ID: <87tvjafbmd.fsf@linux.ibm.com> (raw)
In-Reply-To: <20181218171703.GA22729@infradead.org>
Christoph Hellwig <hch@infradead.org> writes:
> This series seems to miss patches 1 and 2.
https://lore.kernel.org/linuxppc-dev/20181218094137.13732-2-aneesh.kumar@linux.ibm.com/
https://lore.kernel.org/linuxppc-dev/20181218094137.13732-3-aneesh.kumar@linux.ibm.com/
-aneesh
next prev parent reply other threads:[~2018-12-19 3:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 9:41 [PATCH V4 0/5] NestMMU pte upgrade workaround for mprotect Aneesh Kumar K.V
2018-12-18 9:41 ` Aneesh Kumar K.V
2018-12-18 9:41 ` [PATCH V4 1/5] mm: Update ptep_modify_prot_start/commit to take vm_area_struct as arg Aneesh Kumar K.V
2018-12-18 9:41 ` [PATCH V4 2/5] mm: update ptep_modify_prot_commit to take old pte value " Aneesh Kumar K.V
2018-12-18 9:41 ` [PATCH V4 3/5] arch/powerpc/mm: Nest MMU workaround for mprotect RW upgrade Aneesh Kumar K.V
2018-12-18 9:41 ` Aneesh Kumar K.V
2018-12-18 9:41 ` [PATCH V4 4/5] mm/hugetlb: Add prot_modify_start/commit sequence for hugetlb update Aneesh Kumar K.V
2018-12-18 9:41 ` Aneesh Kumar K.V
2018-12-18 9:41 ` [PATCH V4 5/5] arch/powerpc/mm/hugetlb: NestMMU workaround for hugetlb mprotect RW upgrade Aneesh Kumar K.V
2018-12-18 9:41 ` Aneesh Kumar K.V
2018-12-18 17:22 ` Christoph Hellwig
2018-12-18 17:22 ` Christoph Hellwig
2018-12-19 3:20 ` Aneesh Kumar K.V
2018-12-19 3:20 ` Aneesh Kumar K.V
2018-12-19 6:31 ` Christoph Hellwig
2018-12-19 6:31 ` Christoph Hellwig
2018-12-20 0:30 ` Benjamin Herrenschmidt
2018-12-20 0:30 ` Benjamin Herrenschmidt
2018-12-20 7:11 ` Christoph Hellwig
2018-12-20 7:11 ` Christoph Hellwig
2018-12-18 17:17 ` [PATCH V4 0/5] NestMMU pte upgrade workaround for mprotect Christoph Hellwig
2018-12-18 17:17 ` Christoph Hellwig
2018-12-18 22:30 ` Benjamin Herrenschmidt
2018-12-18 22:30 ` Benjamin Herrenschmidt
2018-12-19 3:18 ` Aneesh Kumar K.V [this message]
2018-12-19 3:18 ` Aneesh Kumar K.V
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=87tvjafbmd.fsf@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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 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.