[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1b7d8261-b501-c118-3bed-9b80983218cb@linuxfoundation.org>
Date: Wed, 7 Apr 2021 16:46:09 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: Brendan Higgins <brendanhiggins@...gle.com>,
Daniel Latypov <dlatypov@...gle.com>
Cc: David Gow <davidgow@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
KUnit Development <kunit-dev@...glegroups.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH] Documentation: kunit: add tips for using
current->kunit_test
On 4/7/21 2:07 PM, Brendan Higgins wrote:
> On Tue, Apr 6, 2021 at 3:51 PM Daniel Latypov <dlatypov@...gle.com> wrote:
>>
>> As of commit 359a376081d4 ("kunit: support failure from dynamic analysis
>> tools"), we can use current->kunit_test to find the current kunit test.
>>
>> Mention this in tips.rst and give an example of how this can be used in
>> conjunction with `test->priv` to pass around state and specifically
>> implement something like mocking.
>> There's a lot more we could go into on that topic, but given that
>> example is already longer than every other "tip" on this page, we just
>> point to the API docs and leave filling in the blanks as an exercise to
>> the reader.
>>
>> Also give an example of kunit_fail_current_test().
>>
>> Signed-off-by: Daniel Latypov <dlatypov@...gle.com>
>
> Reviewed-by: Brendan Higgins <brendanhiggins@...gle.com>
>
Thank you. Applied to linux-kseftest kunit branch for 5.13-rc1
thanks,
-- Shuah
Powered by blists - more mailing lists