From: David Gow <davidgow@google.com>
To: trishalfonso@google.com, brendanhiggins@google.com,
aryabinin@virtuozzo.com, dvyukov@google.com, mingo@redhat.com,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, andreyknvl@google.com,
shuah@kernel.org, akpm@linux-foundation.org
Cc: David Gow <davidgow@google.com>,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH v11 4/6] kasan: test: Make KASAN KUnit test comply with naming guidelines
Date: Tue, 4 Aug 2020 21:29:36 -0700 [thread overview]
Message-ID: <20200805042938.2961494-5-davidgow@google.com> (raw)
In-Reply-To: <20200805042938.2961494-1-davidgow@google.com>
The proposed KUnit test naming guidelines[1] suggest naming KUnit test
modules [suite]_kunit (and hence test source files [suite]_kunit.c).
Rename test_kunit.c to kasan_kunit.c to comply with this, and be
consistent with other KUnit tests.
[1]: https://lore.kernel.org/linux-kselftest/20200702071416.1780522-1-davidgow@google.com/
Signed-off-by: David Gow <davidgow@google.com>
---
lib/Makefile | 6 +++---
lib/{test_kasan.c => kasan_kunit.c} | 0
2 files changed, 3 insertions(+), 3 deletions(-)
rename lib/{test_kasan.c => kasan_kunit.c} (100%)
diff --git a/lib/Makefile b/lib/Makefile
index adaebfac81c9..8a530bf7078c 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -60,9 +60,9 @@ CFLAGS_test_bitops.o += -Werror
obj-$(CONFIG_TEST_SYSCTL) += test_sysctl.o
obj-$(CONFIG_TEST_HASH) += test_hash.o test_siphash.o
obj-$(CONFIG_TEST_IDA) += test_ida.o
-obj-$(CONFIG_KASAN_KUNIT_TEST) += test_kasan.o
-CFLAGS_test_kasan.o += -fno-builtin
-CFLAGS_test_kasan.o += $(call cc-disable-warning, vla)
+obj-$(CONFIG_KASAN_KUNIT_TEST) += kasan_kunit.o
+CFLAGS_kasan_kunit.o += -fno-builtin
+CFLAGS_kasan_kunit.o += $(call cc-disable-warning, vla)
obj-$(CONFIG_TEST_KASAN_MODULE) += test_kasan_module.o
obj-$(CONFIG_TEST_UBSAN) += test_ubsan.o
CFLAGS_test_ubsan.o += $(call cc-disable-warning, vla)
diff --git a/lib/test_kasan.c b/lib/kasan_kunit.c
similarity index 100%
rename from lib/test_kasan.c
rename to lib/kasan_kunit.c
--
2.28.0.163.g6104cc2f0b6-goog
next prev parent reply other threads:[~2020-08-05 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 4:29 [PATCH v11 0/6] KASAN-KUnit Integration David Gow
2020-08-05 4:29 ` [PATCH v11 1/6] Add KUnit Struct to Current Task David Gow
2020-08-05 4:29 ` [PATCH v11 2/6] KUnit: KASAN Integration David Gow
2020-08-05 4:29 ` [PATCH v11 3/6] KASAN: Port KASAN Tests to KUnit David Gow
2020-08-07 13:10 ` Andrey Konovalov
2020-08-05 4:29 ` David Gow [this message]
2020-08-05 4:29 ` [PATCH v11 5/6] KASAN: Testing Documentation David Gow
2020-08-05 4:29 ` [PATCH v11 6/6] mm: kasan: Do not panic if both panic_on_warn and kasan_multishot set David Gow
2020-08-07 13:14 ` [PATCH v11 0/6] KASAN-KUnit Integration Andrey Konovalov
2020-08-08 3:26 ` David Gow
2020-08-10 13:58 ` Andrey Konovalov
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=20200805042938.2961494-5-davidgow@google.com \
--to=davidgow@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=brendanhiggins@google.com \
--cc=dvyukov@google.com \
--cc=juri.lelli@redhat.com \
--cc=kasan-dev@googlegroups.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=trishalfonso@google.com \
--cc=vincent.guittot@linaro.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