From: Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>
Cc: linux-kselftest@vger.kernel.org,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Kees Cook" <keescook@chromium.org>,
"Nikolai Kondrashov" <spbnick@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-doc@vger.kernel.org,
"Brendan Higgins" <brendanhiggins@google.com>,
"Rae Moar" <rmoar@google.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Maíra Canal" <mairacanal@riseup.net>,
mauro.chehab@intel.com, "David Gow" <davidgow@google.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Arthur Grillo" <arthurgrillo@riseup.net>,
kunit-dev@googlegroups.com
Subject: Re: [PATCH RFC 2/2] drm: add documentation for drm_buddy_test kUnit test
Date: Thu, 13 Jul 2023 15:19:58 +0530 [thread overview]
Message-ID: <5f9e75bb-95ae-7f7d-24ce-8c69acf7b94e@amd.com> (raw)
In-Reply-To: <c1d632a3-4e5b-6ab9-3ac1-cb4d696becf9@amd.com>
[-- Attachment #1: Type: text/plain, Size: 3305 bytes --]
Looks good, Feel free to add Reviewed-by: Arunpravin Paneer Selvam
<Arunpravin.PaneerSelvam@amd.com>
Regards,
Arun.
On 7/13/2023 12:09 PM, Christian König wrote:
> [Adding Arun]
>
> Am 12.07.23 um 16:28 schrieb Mauro Carvalho Chehab:
>> As an example for the new documentation tool, add a documentation
>> for drm_buddy_test.
>>
>> I opted to place this on a completely different directory, in order
>> to make easier to test the feature with:
>>
>> $ make SPHINXDIRS="tests" htmldocs
>>
>> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
>
> Acked-by: Christian König <christian.koenig@amd.com>
>
> Arun please take a look as well.
>
> Thanks,
> Christian.
>
>> ---
>>
>> To avoid mailbombing on a large number of people, only mailing lists
>> were C/C on the cover.
>> See [PATCH RFC 0/2] at:
>> https://lore.kernel.org/all/cover.1689171160.git.mchehab@kernel.org/
>>
>> Documentation/index.rst | 2 +-
>> Documentation/tests/index.rst | 6 ++++++
>> Documentation/tests/kunit.rst | 5 +++++
>> drivers/gpu/drm/tests/drm_buddy_test.c | 12 ++++++++++++
>> 4 files changed, 24 insertions(+), 1 deletion(-)
>> create mode 100644 Documentation/tests/index.rst
>> create mode 100644 Documentation/tests/kunit.rst
>>
>> diff --git a/Documentation/index.rst b/Documentation/index.rst
>> index 9dfdc826618c..80a6ce14a61a 100644
>> --- a/Documentation/index.rst
>> +++ b/Documentation/index.rst
>> @@ -60,7 +60,7 @@ Various other manuals with useful information for
>> all kernel developers.
>> fault-injection/index
>> livepatch/index
>> rust/index
>> -
>> + test/index
>> User-oriented documentation
>> ===========================
>> diff --git a/Documentation/tests/index.rst
>> b/Documentation/tests/index.rst
>> new file mode 100644
>> index 000000000000..bfc39eb5c0aa
>> --- /dev/null
>> +++ b/Documentation/tests/index.rst
>> @@ -0,0 +1,6 @@
>> +========================
>> +Kunit documentation test
>> +========================
>> +
>> +.. toctree::
>> + kunit
>> diff --git a/Documentation/tests/kunit.rst
>> b/Documentation/tests/kunit.rst
>> new file mode 100644
>> index 000000000000..6ffc151988a0
>> --- /dev/null
>> +++ b/Documentation/tests/kunit.rst
>> @@ -0,0 +1,5 @@
>> +Kunit tests
>> +-----------
>> +
>> +.. include-test:: drivers/gpu/drm/tests/drm_buddy_test.c
>> +
>> diff --git a/drivers/gpu/drm/tests/drm_buddy_test.c
>> b/drivers/gpu/drm/tests/drm_buddy_test.c
>> index 09ee6f6af896..dd6c5afd6cd6 100644
>> --- a/drivers/gpu/drm/tests/drm_buddy_test.c
>> +++ b/drivers/gpu/drm/tests/drm_buddy_test.c
>> @@ -737,6 +737,18 @@ static int drm_buddy_suite_init(struct
>> kunit_suite *suite)
>> return 0;
>> }
>> +/**
>> + * KTEST_SUITE: set of tests for drm buddy alloc
>> + * Scope: drm subsystem
>> + * Mega feature: drm
>> + * Feature: buddy_alloc
>> + *
>> + * KTEST_TEST: drm_test_buddy_alloc_%s
>> + * Description: Run DRM buddy allocation %arg[1] test
>> + *
>> + * arg[1].values: limit, range, optimistic, smoke, pathological
>> + */
>> +
>> static struct kunit_case drm_buddy_tests[] = {
>> KUNIT_CASE(drm_test_buddy_alloc_limit),
>> KUNIT_CASE(drm_test_buddy_alloc_range),
>
[-- Attachment #2: Type: text/html, Size: 5983 bytes --]
next prev parent reply other threads:[~2023-07-13 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 14:28 [PATCH RFC 0/2] Add support for inlined documentation for kunit and kselftests Mauro Carvalho Chehab
2023-07-12 14:28 ` [PATCH RFC 2/2] drm: add documentation for drm_buddy_test kUnit test Mauro Carvalho Chehab
2023-07-12 15:03 ` Jani Nikula
2023-07-13 4:25 ` Mauro Carvalho Chehab
2023-07-13 6:39 ` Christian König
2023-07-13 9:49 ` Arunpravin Paneer Selvam [this message]
2023-07-13 21:31 ` Rae Moar
2023-09-01 7:11 ` Mauro Carvalho Chehab
2023-09-06 22:39 ` Rae Moar
2023-07-13 22:49 ` Rae Moar
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=5f9e75bb-95ae-7f7d-24ce-8c69acf7b94e@amd.com \
--to=arunpravin.paneerselvam@amd.com \
--cc=Jason@zx2c4.com \
--cc=arthurgrillo@riseup.net \
--cc=brendanhiggins@google.com \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=djwong@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mairacanal@riseup.net \
--cc=mauro.chehab@intel.com \
--cc=mchehab@kernel.org \
--cc=rmoar@google.com \
--cc=skhan@linuxfoundation.org \
--cc=spbnick@gmail.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