From: Shuah Khan <skhan@linuxfoundation.org>
To: Yi Lai <yi1.lai@intel.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, wad@chromium.org, luto@amacapital.net,
kees@kernel.org, thomas.weissschuh@linutronix.de,
usama.anjum@collabora.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests/kselftest_harness: Add harness-selftest.expected to TEST_FILES
Date: Tue, 16 Sep 2025 18:06:29 -0600 [thread overview]
Message-ID: <39da8772-a44f-466b-ba2e-425ae464abb2@linuxfoundation.org> (raw)
In-Reply-To: <20250909082619.584470-1-yi1.lai@intel.com>
On 9/9/25 02:26, Yi Lai wrote:
> The harness-selftest.expected is not installed in INSTALL_PATH.
> Attempting to execute harness-selftest.sh shows warning:
>
> diff: ./kselftest_harness/harness-selftest.expected: No such file or
> directory
>
> Add harness-selftest.expected to TEST_FILES.
>
> Fixes: df82ffc5a3c1 ("selftests: harness: Add kselftest harness selftest")
> Signed-off-by: Yi Lai <yi1.lai@intel.com>
> Reviewed-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> tools/testing/selftests/kselftest_harness/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/kselftest_harness/Makefile b/tools/testing/selftests/kselftest_harness/Makefile
> index 0617535a6ce4..d2369c01701a 100644
> --- a/tools/testing/selftests/kselftest_harness/Makefile
> +++ b/tools/testing/selftests/kselftest_harness/Makefile
> @@ -2,6 +2,7 @@
>
> TEST_GEN_PROGS_EXTENDED := harness-selftest
> TEST_PROGS := harness-selftest.sh
> +TEST_FILES := harness-selftest.expected
> EXTRA_CLEAN := harness-selftest.seen
>
> include ../lib.mk
Applied to linux-kselftest next for Linux 6.18-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2025-09-17 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 8:26 [PATCH v2] selftests/kselftest_harness: Add harness-selftest.expected to TEST_FILES Yi Lai
2025-09-17 0:06 ` Shuah Khan [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=39da8772-a44f-466b-ba2e-425ae464abb2@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=shuah@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=usama.anjum@collabora.com \
--cc=wad@chromium.org \
--cc=yi1.lai@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.