From: glittao@gmail.com
To: brendanhiggins@google.com, cl@linux.com, penberg@kernel.org,
rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, vbabka@suse.cz
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, linux-mm@kvack.org, elver@google.com,
dlatypov@google.com, Oliver Glitta <glittao@gmail.com>
Subject: [PATCH] mm/slub, kunit: add a KUnit test for SLUB debugging functionality-fix
Date: Wed, 12 May 2021 16:06:56 +0200 [thread overview]
Message-ID: <20210512140656.12083-1-glittao@gmail.com> (raw)
In-Reply-To: <20210511150734.3492-2-glittao@gmail.com>
From: Oliver Glitta <glittao@gmail.com>
Remove unused function test_exit(), from SLUB KUnit test.
Reported-by: Marco Elver <elver@google.com>
Signed-off-by: Oliver Glitta <glittao@gmail.com>
---
lib/slub_kunit.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/lib/slub_kunit.c b/lib/slub_kunit.c
index f28965f64ef6..8662dc6cb509 100644
--- a/lib/slub_kunit.c
+++ b/lib/slub_kunit.c
@@ -129,8 +129,6 @@ static int test_init(struct kunit *test)
return 0;
}
-static void test_exit(struct kunit *test) {}
-
static struct kunit_case test_cases[] = {
KUNIT_CASE(test_clobber_zone),
@@ -147,7 +145,6 @@ static struct kunit_case test_cases[] = {
static struct kunit_suite test_suite = {
.name = "slub_test",
.init = test_init,
- .exit = test_exit,
.test_cases = test_cases,
};
kunit_test_suite(test_suite);
--
2.31.1.272.g89b43f80a5
next prev parent reply other threads:[~2021-05-12 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 15:07 [PATCH v5 1/3] kunit: make test->lock irq safe glittao
2021-05-11 15:07 ` [PATCH v5 2/3] mm/slub, kunit: add a KUnit test for SLUB debugging functionality glittao
2021-05-11 15:16 ` Marco Elver
2021-05-12 10:30 ` Vlastimil Babka
2021-05-12 14:06 ` glittao [this message]
2021-05-13 4:44 ` Andrew Morton
2021-05-13 8:54 ` Marco Elver
2021-05-13 9:32 ` Oliver Glitta
2021-05-11 15:07 ` [PATCH v5 3/3] slub: remove resiliency_test() function glittao
2021-05-12 10:28 ` [PATCH v5 1/3] kunit: make test->lock irq safe Vlastimil Babka
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=20210512140656.12083-1-glittao@gmail.com \
--to=glittao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brendanhiggins@google.com \
--cc=cl@linux.com \
--cc=dlatypov@google.com \
--cc=elver@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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).