From: Abhinav <singhabhinav9051571833@gmail.com>
To: shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Abhinav <singhabhinav9051571833@gmail.com>
Subject: [PATCH v2] Added missing TARGETS in kselftest top level Makefile
Date: Mon, 2 Oct 2023 17:16:35 +0530 [thread overview]
Message-ID: <20231002114635.1567809-1-singhabhinav9051571833@gmail.com> (raw)
In-Reply-To: <2023100251-recycled-purist-1ea5@gregkh>
Some tests like dma, ia64, etc. were not present in top level of
selftest Makefile, so when someone ran 'make run_tests' they would miss
these tests. This patches adds those left out tests.
Signed-off-by: Abhinav <singhabhinav9051571833@gmail.com>
---
I removed sched, safesetid and filelock from the Makefile, because these
tests were actually triggered when we run 'make run_tests' even though it
has not been mentioned explicitly inside top level Makefile of selftest.
tools/testing/selftests/Makefile | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tools/testing/selftests/Makefile b/tools/testing/selftests/Makefile
index 8d9b2341b79a..dc138c1dcb4b 100644
--- a/tools/testing/selftests/Makefile
+++ b/tools/testing/selftests/Makefile
@@ -13,6 +13,7 @@ TARGETS += core
TARGETS += cpufreq
TARGETS += cpu-hotplug
TARGETS += damon
+TARGETS += dma
TARGETS += dmabuf-heaps
TARGETS += drivers/dma-buf
TARGETS += drivers/s390x/uvdevice
@@ -32,17 +33,21 @@ TARGETS += ftrace
TARGETS += futex
TARGETS += gpio
TARGETS += hid
+TARGETS += ia64
TARGETS += intel_pstate
TARGETS += iommu
TARGETS += ipc
TARGETS += ir
TARGETS += kcmp
TARGETS += kexec
+TARGETS += kmod
TARGETS += kvm
TARGETS += landlock
TARGETS += lib
TARGETS += livepatch
TARGETS += lkdtm
+TARGETS += locking
+TARGETS += media_tests
TARGETS += membarrier
TARGETS += memfd
TARGETS += memory-hotplug
@@ -66,6 +71,7 @@ TARGETS += pid_namespace
TARGETS += powerpc
TARGETS += prctl
TARGETS += proc
+TARGETS += ptp
TARGETS += pstore
TARGETS += ptrace
TARGETS += openat2
@@ -99,6 +105,7 @@ TARGETS += user
TARGETS += user_events
TARGETS += vDSO
TARGETS += mm
+TARGETS += watchdog
TARGETS += x86
TARGETS += zram
#Please keep the TARGETS list alphabetically sorted
--
2.34.1
next prev parent reply other threads:[~2023-10-02 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 19:41 [PATCH] " Abhinav
2023-10-01 6:07 ` Greg KH
2023-10-02 7:27 ` [PATCH v2] " Abhinav
2023-10-02 8:58 ` Greg KH
2023-10-02 11:46 ` Abhinav [this message]
2023-10-02 14:34 ` Shuah Khan
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=20231002114635.1567809-1-singhabhinav9051571833@gmail.com \
--to=singhabhinav9051571833@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.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
all inboxes | Powered by JetHome®