From: Karl Mehltretter <kmehltretter@gmail.com>
To: Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <david@davidgow.net>, Rae Moar <raemoar63@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Marie Zhussupova <marievic@google.com>,
kunit-dev@googlegroups.com
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] kunit: Fix kunit_register_params_array() reference in kernel-doc
Date: Fri, 11 Sep 2026 22:39:01 +0200 [thread overview]
Message-ID: <20260911203901.95078-1-kmehltretter@gmail.com> (raw)
The kernel-doc comment of KUNIT_CASE_PARAM_WITH_INIT() refers to
kunit_register_param_array, which does not exist. The name is
kunit_register_params_array. Say kunit_register_params_array.
Fixes: b820b9077b7f ("kunit: Enable direct registration of parameter arrays to a KUnit test")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
include/kunit/test.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/kunit/test.h b/include/kunit/test.h
index da5312e0dfa57f37a7e96c9e618b03b0947ede8b..55548dc54444f8c9f9e9319fbc263d93c0a56093 100644
--- a/include/kunit/test.h
+++ b/include/kunit/test.h
@@ -239,7 +239,7 @@ static inline char *kunit_status_to_ok_not_ok(enum kunit_status status)
* that were not managed by the parameterized test, and any other teardown logic.
*
* Note: If you are registering a parameter array in param_init() with
- * kunit_register_param_array() then you need to pass kunit_array_gen_params()
+ * kunit_register_params_array() then you need to pass kunit_array_gen_params()
* to this as the generator function.
*/
#define KUNIT_CASE_PARAM_WITH_INIT(test_name, gen_params, init, exit) \
reply other threads:[~2026-09-11 20:40 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=20260911203901.95078-1-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=david@davidgow.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=marievic@google.com \
--cc=raemoar63@gmail.com \
--cc=skhan@linuxfoundation.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®