From: David Gow <davidgow@google.com>
To: Yuya Ishikawa <ishikawa.yuy-00@jp.fujitsu.com>
Cc: Brendan Higgins <brendan.higgins@linux.dev>,
Rae Moar <rmoar@google.com>, Jonathan Corbet <corbet@lwn.net>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, misono.tomohiro@fujitsu.com
Subject: Re: [PATCH] Documentation: kunit: add description of kunit.enable parameter
Date: Tue, 21 Oct 2025 14:50:07 +0800 [thread overview]
Message-ID: <CABVgOSmC5jONnuNHt3YZvMyFK83Y26KWYYFwP6TAoOKnCwAGeA@mail.gmail.com> (raw)
In-Reply-To: <20251021030605.41610-1-ishikawa.yuy-00@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Tue, 21 Oct 2025 at 11:02, Yuya Ishikawa
<ishikawa.yuy-00@jp.fujitsu.com> wrote:
>
> The current KUnit documentation does not mention the kunit.enable
> kernel parameter, making it unclear how to troubleshoot cases where
> KUnit tests do not run as expected.
> Add a note explaining kunit.enable parmaeter. Disabling this parameter
> prevents all KUnit tests from running even if CONFIG_KUNIT is enabled.
>
> Signed-off-by: Yuya Ishikawa <ishikawa.yuy-00@jp.fujitsu.com>
> ---
Looks good to me, thanks!
Reviewed-by: David Gow <davidgow@google.com>
Cheers,
-- David
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5281 bytes --]
prev parent reply other threads:[~2025-10-21 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 3:06 Yuya Ishikawa
2025-10-21 6:50 ` David Gow [this message]
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=CABVgOSmC5jONnuNHt3YZvMyFK83Y26KWYYFwP6TAoOKnCwAGeA@mail.gmail.com \
--to=davidgow@google.com \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=ishikawa.yuy-00@jp.fujitsu.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=misono.tomohiro@fujitsu.com \
--cc=rmoar@google.com \
--cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox