From: Andrew Morton <akpm@linux-foundation.org>
To: Pavithra <pavrampu@linux.ibm.com>
Cc: shuah@kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, ritesh.list@gmail.com,
david@kernel.org, ziy@nvidia.com, mhocko@kernel.org,
osalvador@suse.de, lorenzo.stoakes@oracle.com, dev.jain@arm.com,
Liam.Howlett@oracle.com, linmiaohe@huawei.com
Subject: Re: [PATCH] selftests/mm/run_vmtests.sh: Fix protection_keys binary name in run_vmtests.sh
Date: Sun, 31 May 2026 23:22:01 -0700 [thread overview]
Message-ID: <20260531232201.7613f20b850f0bff4f133f3b@linux-foundation.org> (raw)
In-Reply-To: <20260601061314.898388-1-pavrampu@linux.ibm.com>
On Mon, 1 Jun 2026 11:43:14 +0530 Pavithra <pavrampu@linux.ibm.com> wrote:
> we have protection_keys_32 and protection_keys_64 tests mentioned in
> run_vmtests.sh but the binary name is protection_keys with current
> kernel,
Is it?
Makefile has:
VMTARGETS := protection_keys
VMTARGETS += pkey_sighandler_tests
BINARIES_32 := $(VMTARGETS:%=%_32)
BINARIES_64 := $(VMTARGETS:%=%_64)
hp2:/usr/src/mm/tools/testing/selftests/mm> ls -l prot*
-rwxrwxr-x 1 akpm akpm 117792 May 31 23:20 protection_keys_64
-rw-rw-r-- 1 akpm akpm 48448 May 31 21:54 protection_keys.c
prev parent reply other threads:[~2026-06-01 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 6:13 [PATCH] selftests/mm/run_vmtests.sh: Fix protection_keys binary name in run_vmtests.sh Pavithra
2026-06-01 6:22 ` Andrew Morton [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=20260531232201.7613f20b850f0bff4f133f3b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=pavrampu@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=shuah@kernel.org \
--cc=ziy@nvidia.com \
/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