From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 0/5] VPHN parsing fixes
Date: Tue, 17 Mar 2015 16:41:39 +0530 [thread overview]
Message-ID: <55080BEB.6010701@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150223151412.21565.2251.stgit@bahia.local>
On 02/23/2015 08:44 PM, Greg Kurz wrote:
> Michael,
>
> As suggested in...
>
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-February/124647.html
>
> ... I repost the whole series with an extra patch to implement selftests
> for VPHN (this is the only change between v2 and v3).
>
> Please review.
[Including the reworked test case from Michael]
Reviewed-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Tested-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
prev parent reply other threads:[~2015-03-17 11:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:14 [PATCH v3 0/5] VPHN parsing fixes Greg Kurz
2015-02-23 15:14 ` [PATCH v3 1/5] powerpc/vphn: clarify the H_HOME_NODE_ASSOCIATIVITY API Greg Kurz
2015-02-23 15:14 ` [PATCH v3 2/5] powerpc/vphn: move endianness fixing to vphn_unpack_associativity() Greg Kurz
2015-02-23 15:14 ` [PATCH v3 3/5] powerpc/vphn: move VPHN parsing logic to a separate file Greg Kurz
2015-02-23 15:14 ` [PATCH v3 4/5] powerpc/vphn: parsing code rewrite Greg Kurz
2015-03-17 9:50 ` Anshuman Khandual
2015-03-17 10:48 ` Greg Kurz
2015-02-23 15:14 ` [PATCH v3 5/5] selftests, powerpc: Add test for VPHN Greg Kurz
2015-03-17 4:21 ` [PATCH v4 5/5] selftests/powerpc: " Michael Ellerman
2015-03-17 11:49 ` Greg Kurz
2015-03-17 22:58 ` Michael Ellerman
2015-03-17 11:11 ` Anshuman Khandual [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=55080BEB.6010701@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).