From: Shuah Khan <skhan@linuxfoundation.org>
To: Sandipan Das <sandipan@linux.ibm.com>,
shuah@kernel.org, linux-kselftest@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
kamalesh@linux.vnet.ibm.com, linux-mm@kvack.org,
mhiramat@kernel.org, aneesh.kumar@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] selftests: vm: Build fixes for powerpc64
Date: Tue, 31 Mar 2020 08:37:04 -0600 [thread overview]
Message-ID: <4837525c-c078-0e33-614e-103514946ff9@linuxfoundation.org> (raw)
In-Reply-To: <cover.1580367152.git.sandipan@linux.ibm.com>
On 1/30/20 12:01 AM, Sandipan Das wrote:
> The second patch was already posted independently but because
> of the changes in the first patch, the second one now depends
> on it. Hence posting it now as a part of this series.
>
> The last version (v2) of the second patch can be found at:
> https://patchwork.ozlabs.org/patch/1225969/
>
> Sandipan Das (2):
> selftests: vm: Do not override definition of ARCH
> selftests: vm: Fix 64-bit test builds for powerpc64le
>
> tools/testing/selftests/vm/Makefile | 4 ++--
> tools/testing/selftests/vm/run_vmtests | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
Michael,
I see your tested-by on these two patches. I will take these
through kselftest fixes.
Sorry for the delay. I assumed these will go through ppc64 or
vm.
thanks,
-- Shuah
next prev parent reply other threads:[~2020-03-31 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 7:01 [PATCH 0/2] selftests: vm: Build fixes for powerpc64 Sandipan Das
2020-01-30 7:01 ` [PATCH 1/2] selftests: vm: Do not override definition of ARCH Sandipan Das
2020-02-11 2:49 ` Michael Ellerman
2020-04-10 15:57 ` Shuah Khan
2020-01-30 7:01 ` [PATCH 2/2] selftests: vm: Fix 64-bit test builds for powerpc64le Sandipan Das
2020-02-11 2:50 ` Michael Ellerman
2020-03-31 14:37 ` Shuah Khan [this message]
2020-04-01 3:37 ` [PATCH 0/2] selftests: vm: Build fixes for powerpc64 Michael Ellerman
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=4837525c-c078-0e33-614e-103514946ff9@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhiramat@kernel.org \
--cc=sandipan@linux.ibm.com \
--cc=shuah@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 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).