[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAFd5g46uNRwDnKHjukU2gBu6wM0kzBragaWBJigbfJkFuQvsFw@mail.gmail.com>
Date: Thu, 28 May 2020 12:47:43 -0700
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Alan Maguire <alan.maguire@...cle.com>
Cc: shuah <shuah@...nel.org>,
Patricia Alfonso <trishalfonso@...gle.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
KUnit Development <kunit-dev@...glegroups.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 kunit-next 2/2] kunit: add support for named resources
On Fri, Mar 27, 2020 at 5:46 AM Alan Maguire <alan.maguire@...cle.com> 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@...cle.com>
FYI, I already gave a reviewed-by for this commit back in v1, so:
Reviewed-by: Brendan Higgins <brendanhiggins@...gle.com>
Powered by blists - more mailing lists