Hi, On Sat, Mar 25, 2023 at 12:31:04PM +0800, David Gow wrote: > Tests for drivers often require a struct device to pass to other > functions. While it's possible to create these with > root_device_register(), or to use something like a platform device, this > is both a misuse of those APIs, and can be difficult to clean up after, > for example, a failed assertion. > > Add two KUnit-specific functions for registering and unregistering a > struct device: > - kunit_device_register() > - kunit_device_unregister() If kunit_device_register() registers an action to clean up after the test has ran, I'm not sure why do we need kunit_device_unregister() I guess the typical test would just call kunit_device_register() and be done with it, right? Maxime
