From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
npiggin@gmail.com, paulus@samba.org
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [v4, 1/8] powerpc/mm/hash64: Add a variable to track the end of IO mapping
Date: Mon, 22 Apr 2019 00:19:11 +1000 (AEST) [thread overview]
Message-ID: <44nBfS0hGvz9sNk@ozlabs.org> (raw)
In-Reply-To: <20190417125920.785-2-aneesh.kumar@linux.ibm.com>
On Wed, 2019-04-17 at 12:59:13 UTC, "Aneesh Kumar K.V" wrote:
> This makes it easy to update the region mapping in the later patch
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Patches 1-7 applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/a35a3c6f60657812366fca86a9ce71df
cheers
next prev parent reply other threads:[~2019-04-21 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 12:59 [PATCH v4 0/8] Update hash MMU kernel mapping to be in sync with radix Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 1/8] powerpc/mm/hash64: Add a variable to track the end of IO mapping Aneesh Kumar K.V
2019-04-21 14:19 ` Michael Ellerman [this message]
2019-04-17 12:59 ` [PATCH v4 2/8] powerpc/mm/hash64: Map all the kernel regions in the same 0xc range Aneesh Kumar K.V
2019-04-17 22:27 ` kbuild test robot
2019-04-18 3:47 ` Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 3/8] powerpc/mm: Validate address values against different region limits Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 4/8] powerpc/mm: Drop the unnecessary region check Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 5/8] powerpc/mm/hash: Simplify the region id calculation Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 6/8] powerpc/mm: Print kernel map details to dmesg Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 7/8] powerpc/mm/hash: Rename KERNEL_REGION_ID to LINEAR_MAP_REGION_ID Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 8/8] powerpc/mm/hash/4K: Update the vmalloc start for hash 4K config 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=44nBfS0hGvz9sNk@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--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 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).