linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@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: [4/6] powerpc/mm/hash: Compute the segment size correctly for ISA 3.0
Date: Fri, 10 Jun 2016 13:26:32 +1000 (AEST)	[thread overview]
Message-ID: <3rQndh1BTCz9sdQ@ozlabs.org> (raw)
In-Reply-To: <1463644472-10158-4-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

On Thu, 2016-19-05 at 07:54:30 UTC, "Aneesh Kumar K.V" wrote:
> PowerISA 3.0 encodes the segment size in the second half of hash page
> table entry. Update hpte_decode accordingly.
> 
> Fixes: 50de596de8be ("powerpc/mm/hash: Add support for Power9 Hash")
> 
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>

Applied to powerpc fixes, thanks.

https://git.kernel.org/powerpc/c/3b6d1eb7ea65f4aa64115cf9ba

cheers

  reply	other threads:[~2016-06-10  3:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19  7:54 [PATCH 1/6] powerpc/mm/radix: Update LPCR only if it is powernv Aneesh Kumar K.V
2016-05-19  7:54 ` [PATCH 2/6] powerpc/mm/radix: Update PID switch sequence Aneesh Kumar K.V
2016-05-19  7:54 ` [PATCH 3/6] powerpc/mm/hash: Update SDR1 size encoding as documented in ISA 3.0 Aneesh Kumar K.V
2016-05-19  7:54 ` [PATCH 4/6] powerpc/mm/hash: Compute the segment size correctly for " Aneesh Kumar K.V
2016-06-10  3:26   ` Michael Ellerman [this message]
2016-05-19  7:54 ` [PATCH 5/6] powerpc/mm: Make MMU_FTR_RADIX a MMU family feature Aneesh Kumar K.V
2016-05-19  7:54 ` [PATCH 6/6] powerpc/mm/hash: Add helper for finding SLBE LLP encoding 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=3rQndh1BTCz9sdQ@ozlabs.org \
    --to=mpe@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 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).