From: Matti Vaittinen <mazziesaccount@gmail.com>
To: davidgow@google.com, Rae Moar <rmoar@google.com>,
Brendan Higgins <brendan.higgins@linux.dev>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Boyd <sboyd@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Kees Cook <keescook@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Maxime Ripard <mripard@kernel.org>
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH 2/4] fortify: test: Use kunit_device
Date: Tue, 5 Dec 2023 10:39:20 +0200 [thread overview]
Message-ID: <644e095d-4c01-4e8d-8036-3c04ada405f2@gmail.com> (raw)
In-Reply-To: <20231205-kunit_bus-v1-2-635036d3bc13@google.com>
On 12/5/23 09:31, davidgow@google.com wrote:
> Using struct root_device to create fake devices for tests is something
> of a hack. The new struct kunit_device is meant for this purpose, so use
> it instead.
>
> Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2023-12-05 8:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 7:31 [PATCH 0/4] kunit: Add helpers for creating test-managed devices davidgow
2023-12-05 7:31 ` [PATCH 1/4] kunit: Add APIs for managing devices davidgow
2023-12-05 8:30 ` Matti Vaittinen
2023-12-06 7:43 ` David Gow
2023-12-05 9:00 ` Maxime Ripard
2023-12-05 9:02 ` Amadeusz Sławiński
2023-12-05 13:53 ` kernel test robot
2023-12-05 14:59 ` kernel test robot
2023-12-05 15:10 ` kernel test robot
2023-12-05 16:05 ` kernel test robot
2023-12-05 17:30 ` Greg Kroah-Hartman
2023-12-06 7:44 ` David Gow
2023-12-07 2:29 ` Greg Kroah-Hartman
2023-12-05 7:31 ` [PATCH 2/4] fortify: test: Use kunit_device davidgow
2023-12-05 8:39 ` Matti Vaittinen [this message]
2023-12-06 21:07 ` Kees Cook
2023-12-08 7:38 ` David Gow
2023-12-05 7:31 ` [PATCH 3/4] overflow: Replace fake root_device with kunit_device davidgow
2023-12-05 8:46 ` Matti Vaittinen
2023-12-05 7:31 ` [PATCH 4/4] ASoC: topology: Replace fake root_device with kunit_device in tests davidgow
2023-12-05 9:02 ` Amadeusz Sławiński
2023-12-05 13:03 ` Mark Brown
2023-12-05 9:04 ` [PATCH] drm/tests: Switch to kunit devices Maxime Ripard
2023-12-06 16:31 ` kernel test robot
2023-12-06 16:42 ` kernel test robot
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=644e095d-4c01-4e8d-8036-3c04ada405f2@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=perex@perex.cz \
--cc=rmoar@google.com \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).