On Fri, Mar 27, 2020 at 5:46 AM Alan Maguire <alan.maguire@xxxxxxxxxx> wrote: > > The kunit resources API allows for custom initialization and > cleanup code (init/fini); here a new resource add function sets > the "struct kunit_resource" "name" field, and calls the standard > add function. Having a simple way to name resources is > useful in cases such as multithreaded tests where a set of > resources are shared among threads; a pointer to the > "struct kunit *" test state then is all that is needed to > retrieve and use named resources. Support is provided to add, > find and destroy named resources; the latter two are simply > wrappers that use a "match-by-name" callback. > > If an attempt to add a resource with a name that already exists > is made kunit_add_named_resource() will return -EEXIST. > > Signed-off-by: Alan Maguire <alan.maguire@xxxxxxxxxx> FYI, I already gave a reviewed-by for this commit back in v1, so: Reviewed-by: Brendan Higgins <brendanhiggins@xxxxxxxxxx>
