From: Karolina Stolarek <karolina.stolarek@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: "Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v8 0/8] Improve test coverage of TTM
Date: Wed, 6 Dec 2023 12:28:14 +0100 [thread overview]
Message-ID: <817fdcb9-e4f6-4f8d-8311-27b0b5fd444e@intel.com> (raw)
In-Reply-To: <ZW9ENFoRHlec4HNE@ashyti-mobl2.lan>
Hi Andi,
On 5.12.2023 16:39, Andi Shyti wrote:
> Hi Karolina and Christian,
>
>> Karolina Stolarek (8): drm/ttm/tests: Add tests for ttm_resource
>> and ttm_sys_man drm/ttm/tests: Add tests for ttm_tt drm/ttm/tests:
>> Add tests for ttm_bo functions drm/ttm/tests: Fix argument in
>> ttm_tt_kunit_init() drm/ttm/tests: Use an init function from the
>> helpers lib drm/ttm/tests: Test simple BO creation and validation
>> drm/ttm/tests: Add tests with mock resource managers drm/ttm/tests:
>> Add test cases dependent on fence signaling
>
> I see that all these files (and previous patches, as well) don't have
> a consistent prefix system, like kunit_ttm_*. But they all start with
> ttm_*, thread_*, drm_*, etc, which makes it a bit difficult to follow
> and grep through.
I see what you mean. As for ttm_* part, I decided to keep it as it is
based on what was in DRM KUnit tests and helpers lib. Almost all
functions and subtests start with drm_*, and as I'm working on TTM
tests, ttm_* prefix seemed like a natural choice. With thread_*, I could
add ttm_kunit_* in front of it, but not sure what would be the benefit
of doing this.
To be honest, I haven't considered using kunit_* prefix here. In the
code context, it's obvious these are kunit tests, and repeating that
information would make already long function/struct names even longer.
I had a quick glance at other KUnit tests in the kernel and this seems
to be the case, no kunit_* prefixes are used.
> Can we please maintain a consistent prefix system?
>
> I know it looks bad to come out with it after this series (and
> previous work too) has been out for several months already. I need to
> say my "mea culpa" as well as I've been in the review loop, as well.
After this series, I plan to send a small one to wrap up my work in this
field. How about adding a TODO to clean these up? I mean, that's
just how I see it, I'd like to hear Christian's thoughts on this.
All the best,
Karolina
next prev parent reply other threads:[~2023-12-06 11:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 12:02 [PATCH v8 0/8] Improve test coverage of TTM Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 1/8] drm/ttm/tests: Add tests for ttm_resource and ttm_sys_man Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 2/8] drm/ttm/tests: Add tests for ttm_tt Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 3/8] drm/ttm/tests: Add tests for ttm_bo functions Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 4/8] drm/ttm/tests: Fix argument in ttm_tt_kunit_init() Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 5/8] drm/ttm/tests: Use an init function from the helpers lib Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 6/8] drm/ttm/tests: Test simple BO creation and validation Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 7/8] drm/ttm/tests: Add tests with mock resource managers Karolina Stolarek
2023-11-29 12:02 ` [PATCH v8 8/8] drm/ttm/tests: Add test cases dependent on fence signaling Karolina Stolarek
2023-12-05 15:29 ` Andi Shyti
2023-12-06 11:49 ` Karolina Stolarek
2023-12-05 15:39 ` [PATCH v8 0/8] Improve test coverage of TTM Andi Shyti
2023-12-06 11:28 ` Karolina Stolarek [this message]
2023-12-06 11:46 ` Andi Shyti
2023-12-14 8:20 ` Karolina Stolarek
2023-12-14 10:22 ` Christian König
2023-12-14 14:13 ` Karolina Stolarek
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=817fdcb9-e4f6-4f8d-8311-27b0b5fd444e@intel.com \
--to=karolina.stolarek@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.