From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [V6, 1/4] powerpc/mm/slice: Consolidate return path in slice_get_unmapped_area()
Date: Sun, 1 Apr 2018 01:04:03 +1100 (AEDT) [thread overview]
Message-ID: <40D0bB01P9z9s3B@ozlabs.org> (raw)
In-Reply-To: <20180326100450.18614-2-aneesh.kumar@linux.vnet.ibm.com>
On Mon, 2018-03-26 at 10:04:47 UTC, "Aneesh Kumar K.V" wrote:
> In a following patch, on finding a free area we will need to do
> allocatinon of extra contexts as needed. Consolidating the return path
> for slice_get_unmapped_area() will make that easier.
>
> Split into a separate patch to make review easy.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/0dea04b288c06654b0de3563c5b8cd
cheers
next prev parent reply other threads:[~2018-03-31 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 10:04 [PATCH V6 0/4] Add support for 4PB virtual address space on hash Aneesh Kumar K.V
2018-03-26 10:04 ` [PATCH V6 1/4] powerpc/mm/slice: Consolidate return path in slice_get_unmapped_area() Aneesh Kumar K.V
2018-03-31 14:04 ` Michael Ellerman [this message]
2018-03-26 10:04 ` [PATCH V6 2/4] powerpc/mm: Add support for handling > 512TB address in SLB miss Aneesh Kumar K.V
2018-04-09 7:19 ` Christophe LEROY
2018-04-09 8:33 ` Aneesh Kumar K.V
2018-04-09 8:55 ` Christophe LEROY
2018-03-26 10:04 ` [PATCH V6 3/4] powerpc/mm/hash64: Increase the VA range Aneesh Kumar K.V
2018-03-26 10:04 ` [PATCH V6 4/4] powerpc/mm/hash: Don't memset pgd table if not needed 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=40D0bB01P9z9s3B@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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.