From: "Maxime Ripard" <mripard@kernel.org>
To: "Brian Norris" <briannorris@chromium.org>
Cc: kunit-dev@googlegroups.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"David Gow" <davidgow@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Maxime Ripard" <mripard@kernel.org>,
"Rae Moar" <rmoar@google.com>,
"\"Rafael J. Wysocki\"" <rafael@kernel.org>,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v3 2/3] drivers: base: test: Enable device model tests with KUNIT_ALL_TESTS
Date: Tue, 17 Dec 2024 07:41:01 +0000 [thread overview]
Message-ID: <17fbc356583050369235d1a23456eb2e@kernel.org> (raw)
In-Reply-To: <20241216201148.535115-3-briannorris@chromium.org>
On Mon, 16 Dec 2024 12:11:43 -0800, Brian Norris wrote:
> Per commit bebe94b53eb7 ("drivers: base: default KUNIT_* fragments to
> KUNIT_ALL_TESTS"), it seems like we should default to KUNIT_ALL_TESTS.
>
> This enables these platform_device tests for common configurations, such
> as with:
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2024-12-17 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 20:11 [PATCH v3 0/3] drivers: base: Don't match device with NULL of_node/fwnode/etc + tests Brian Norris
2024-12-16 20:11 ` [PATCH v3 1/3] drivers: base: Don't match devices with NULL of_node/fwnode/etc Brian Norris
2024-12-19 5:45 ` David Gow
2024-12-20 17:33 ` Shuah Khan
2024-12-20 17:44 ` Greg Kroah-Hartman
2024-12-16 20:11 ` [PATCH v3 2/3] drivers: base: test: Enable device model tests with KUNIT_ALL_TESTS Brian Norris
2024-12-17 7:41 ` Maxime Ripard [this message]
2024-12-19 5:45 ` David Gow
2024-12-16 20:11 ` [PATCH v3 3/3] drivers: base: test: Add ...find_device_by...(... NULL) tests Brian Norris
2024-12-19 5:45 ` David Gow
2024-12-20 17:34 ` Shuah Khan
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=17fbc356583050369235d1a23456eb2e@kernel.org \
--to=mripard@kernel.org \
--cc=briannorris@chromium.org \
--cc=davidgow@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rmoar@google.com \
--cc=robh@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.