From: Arnd Bergmann <arnd@kernel.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>,
Guenter Roeck <linux@roeck-us.net>, Kees Cook <kees@kernel.org>,
Alessandro Carminati <acarmina@redhat.com>,
Dan Carpenter <dan.carpenter@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Rae Moar <rmoar@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 08/10] kunit: add module description for backtrace suppression test
Date: Mon, 24 Mar 2025 18:32:33 +0100 [thread overview]
Message-ID: <20250324173242.1501003-8-arnd@kernel.org> (raw)
In-Reply-To: <20250324173242.1501003-1-arnd@kernel.org>
From: Arnd Bergmann <arnd@arndb.de>
The module was added but has no description:
WARNING: modpost: missing MODULE_DESCRIPTION() in lib/kunit/backtrace-suppression-test.o
Fixes: ebf1c420422a ("kunit: add test cases for backtrace warning suppression")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
lib/kunit/backtrace-suppression-test.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/kunit/backtrace-suppression-test.c b/lib/kunit/backtrace-suppression-test.c
index 8b4125af2481..1ceb30c736d7 100644
--- a/lib/kunit/backtrace-suppression-test.c
+++ b/lib/kunit/backtrace-suppression-test.c
@@ -102,3 +102,4 @@ static struct kunit_suite backtrace_suppression_test_suite = {
kunit_test_suites(&backtrace_suppression_test_suite);
MODULE_LICENSE("GPL");
+MODULE_DESCRIPTION("KUnit test for suppressing warning tracebacks");
--
2.39.5
parent reply other threads:[~2025-03-24 17:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250324173242.1501003-1-arnd@kernel.org>]
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=20250324173242.1501003-8-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=acarmina@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=brendan.higgins@linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=davidgow@google.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=kees@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=masahiroy@kernel.org \
--cc=rmoar@google.com \
--cc=sfr@canb.auug.org.au \
/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