From: akpm@linux-foundation.org
To: elver@google.com, glittao@gmail.com, mm-commits@vger.kernel.org
Subject: [folded-merged] mm-slub-kunit-add-a-kunit-test-for-slub-debugging-functionality-fix.patch removed from -mm tree
Date: Mon, 28 Jun 2021 17:13:49 -0700 [thread overview]
Message-ID: <20210629001349.z6YmIztYp%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm/slub, kunit: add a KUnit test for SLUB debugging functionality-fix
has been removed from the -mm tree. Its filename was
mm-slub-kunit-add-a-kunit-test-for-slub-debugging-functionality-fix.patch
This patch was dropped because it was folded into mm-slub-kunit-add-a-kunit-test-for-slub-debugging-functionality.patch
------------------------------------------------------
From: Oliver Glitta <glittao@gmail.com>
Subject: mm/slub, kunit: add a KUnit test for SLUB debugging functionality-fix
Remove unused function test_exit(), from SLUB KUnit test.
Link: https://lkml.kernel.org/r/20210512140656.12083-1-glittao@gmail.com
Signed-off-by: Oliver Glitta <glittao@gmail.com>
Reported-by: Marco Elver <elver@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/slub_kunit.c | 3 ---
1 file changed, 3 deletions(-)
--- a/lib/slub_kunit.c~mm-slub-kunit-add-a-kunit-test-for-slub-debugging-functionality-fix
+++ a/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);
_
Patches currently in -mm which might be from glittao@gmail.com are
mm-slub-kunit-add-a-kunit-test-for-slub-debugging-functionality.patch
slub-remove-resiliency_test-function.patch
mm-slub-use-stackdepot-to-save-stack-trace-in-objects.patch
reply other threads:[~2021-06-29 0:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210629001349.z6YmIztYp%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=elver@google.com \
--cc=glittao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.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 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.