From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, suxingxing@loongson.cn,
shuah@kernel.org, sandipan@linux.ibm.com,
kirill.shutemov@linux.intel.com, jhubbard@nvidia.com,
dave.hansen@intel.com, bgeffon@google.com,
almasrymina@google.com, harish@linux.ibm.com
Subject: [to-be-updated] selftests-vm-fix-building-protection-keys-test.patch removed from -mm tree
Date: Fri, 18 Dec 2020 11:03:55 -0800 [thread overview]
Message-ID: <20201218190355.MT8V9%akpm@linux-foundation.org> (raw)
The patch titled
Subject: selftests/vm: fix building protection keys test
has been removed from the -mm tree. Its filename was
selftests-vm-fix-building-protection-keys-test.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Harish <harish@linux.ibm.com>
Subject: selftests/vm: fix building protection keys test
The previous patch tries to include a arch check for powerpc using
findstring, which prevents test from building on powerpc arch. Fix
this with filtering using machine type.
Link: https://lkml.kernel.org/r/20201214163951.141399-1-harish@linux.ibm.com
Signed-off-by: Harish <harish@linux.ibm.com>
Cc: Shuah Khan <shuah@kernel.org>
Cc: Sandipan Das <sandipan@linux.ibm.com>
Cc: John Hubbard <jhubbard@nvidia.com>
Cc: Dave Hansen <dave.hansen@intel.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Brian Geffon <bgeffon@google.com>
Cc: Mina Almasry <almasrymina@google.com>
Cc: Xingxing Su <suxingxing@loongson.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
tools/testing/selftests/vm/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/tools/testing/selftests/vm/Makefile~selftests-vm-fix-building-protection-keys-test
+++ a/tools/testing/selftests/vm/Makefile
@@ -65,7 +65,7 @@ TEST_GEN_FILES += $(BINARIES_64)
endif
else
-ifneq (,$(findstring $(ARCH),powerpc))
+ifneq (,$(filter $(MACHINE),ppc64 ppc64le))
TEST_GEN_FILES += protection_keys
endif
_
Patches currently in -mm which might be from harish@linux.ibm.com are
reply other threads:[~2020-12-18 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201218190355.MT8V9%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=bgeffon@google.com \
--cc=dave.hansen@intel.com \
--cc=harish@linux.ibm.com \
--cc=jhubbard@nvidia.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sandipan@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=suxingxing@loongson.cn \
/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