linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Kalpana Shetty <kalpana.shetty@amd.com>,
	akpm@linux-foundation.org, shuah@kernel.org, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/vm: Add protection_keys tests to run_vmtests
Date: Thu, 9 Jun 2022 14:21:20 -0600	[thread overview]
Message-ID: <4b0aab3f-83f4-80f7-6df0-447561f0da88@linuxfoundation.org> (raw)
In-Reply-To: <20220531102556.388-1-kalpana.shetty@amd.com>

On 5/31/22 4:25 AM, Kalpana Shetty wrote:
> Signed-off-by: Kalpana Shetty <kalpana.shetty@amd.com>

Missing commit log - please add a detailed commit log explaining why
this change is necessary.

> ---
>   tools/testing/selftests/vm/run_vmtests.sh | 7 +++++++
>   1 file changed, 7 insertions(+)
> 
> diff --git a/tools/testing/selftests/vm/run_vmtests.sh b/tools/testing/selftests/vm/run_vmtests.sh
> index 41fce8bea929..54a0c28f810c 100755
> --- a/tools/testing/selftests/vm/run_vmtests.sh
> +++ b/tools/testing/selftests/vm/run_vmtests.sh
> @@ -179,4 +179,11 @@ run_test ./ksm_tests -N -m 1
>   # KSM test with 2 NUMA nodes and merge_across_nodes = 0
>   run_test ./ksm_tests -N -m 0
>   
> +# protection_keys tests
> +if [ $VADDR64 -eq 0 ]; then
> +	run_test ./protection_keys_32
> +else
> +	run_test ./protection_keys_64
> +fi
> +
>   exit $exitcode
> 

thanks,
-- Shuah

  parent reply	other threads:[~2022-06-09 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 10:25 [PATCH] selftests/vm: Add protection_keys tests to run_vmtests Kalpana Shetty
2022-05-31 18:40 ` Andrew Morton
2022-06-01  9:14   ` Shetty, Kalpana
2022-06-09 20:21 ` Shuah Khan [this message]
2022-06-10  9:09   ` Shetty, Kalpana

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=4b0aab3f-83f4-80f7-6df0-447561f0da88@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=kalpana.shetty@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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).