From: Vaibhav Jain <vaibhav@linux.ibm.com>
To: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Cc: Vaibhav Jain <vaibhav@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <david@davidgow.net>, Rae Moar <raemoar63@gmail.com>
Subject: [PATCH v3 2/3] rust: kunit: add 'kunit_suite.status' binding to 'kunit_unsafe_test_suite'
Date: Wed, 17 Jun 2026 17:45:22 +0530 [thread overview]
Message-ID: <20260617121535.462459-3-vaibhav@linux.ibm.com> (raw)
In-Reply-To: <20260617121535.462459-1-vaibhav@linux.ibm.com>
Update KUnit Rust binding macro-rule 'kunit_unsafe_test_suite' to add and
initialize the newly introduced 'kunit_suite.status'. Without this
'kunit_suite.status' field is never initialized which is an error for the
Rust compiler.
Suggested-by: David Gow <david@davidgow.net>
Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
---
Changelog
=========
V2->V3:
Patch, not present in earlier version
---
rust/kernel/kunit.rs | 1 +
1 file changed, 1 insertion(+)
diff --git a/rust/kernel/kunit.rs b/rust/kernel/kunit.rs
index a1edf7491579..e07894c72d0d 100644
--- a/rust/kernel/kunit.rs
+++ b/rust/kernel/kunit.rs
@@ -288,6 +288,7 @@ macro_rules! kunit_unsafe_test_suite {
log: ::core::ptr::null_mut(),
suite_init_err: 0,
is_init: false,
+ status: kernel::bindings::kunit_status_KUNIT_SUCCESS,
};
#[used(compiler)]
--
2.54.0
next prev parent reply other threads:[~2026-06-17 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 12:15 [PATCH v3 0/3] kunit: Add support for skipping entire test suites Vaibhav Jain
2026-06-17 12:15 ` [PATCH v3 1/3] kunit: Add ability to skip " Vaibhav Jain
2026-06-20 11:08 ` David Gow
2026-06-17 12:15 ` Vaibhav Jain [this message]
2026-06-20 11:08 ` [PATCH v3 2/3] rust: kunit: add 'kunit_suite.status' binding to 'kunit_unsafe_test_suite' David Gow
2026-06-17 12:15 ` [PATCH v3 3/3] kunit: Add example of test suite that can be skipped at runtime Vaibhav Jain
2026-06-20 11:08 ` David Gow
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=20260617121535.462459-3-vaibhav@linux.ibm.com \
--to=vaibhav@linux.ibm.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=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=raemoar63@gmail.com \
/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®