public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Alex Hung <alex.hung@amd.com>
To: vitaly prosyak <vprosyak@amd.com>,
	Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org, wayne.lin@amd.com,
	Mark.Broadworth@amd.com, Vitaly Prosyak <vitaly.prosyak@amd.com>
Subject: Re: [PATCH 2/3] tools: Add amd_hdr_visual for manual HDR verification
Date: Wed, 18 Mar 2026 14:15:58 -0600	[thread overview]
Message-ID: <9e09a519-b39a-4744-9718-4a05e68a2203@amd.com> (raw)
In-Reply-To: <2467d584-24ca-49a8-a561-bc19416e052d@amd.com>



On 3/18/26 14:13, vitaly prosyak wrote:
>     The file uses igt_main(), igt_fixture(), igt_subtest(), IGT_TEST_DESCRIPTION(),
>     and igt_assert*() -- this is a test, not a tool. IGT tools (e.g., intel_gpu_top,
>     amd_hdmi_compliance) typically have a regular main() with argument parsing. If
>     this is intentionally a test that requires manual visual confirmation, it should
>     go in tests/ (perhaps tests/amdgpu/), not tools/. If it must be a tool, decouple
>     it from the test framework.
> 
>     Alternatively, if the intent is to keep the igt_main() pattern (as
>     amd_hdmi_compliance.c does), then IGT_TEST_DESCRIPTION() is acceptable but the
>     patch description should clarify this is a manual-verification test binary placed
>     in tools/ because it requires human interaction and shouldn't run in CI.

Thank. I will fix it in V2 after I can rebase to another WIP patch series.

  reply	other threads:[~2026-03-18 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 17:51 [PATCH 1/3] lib/igt_hdr: Extract HDR helpers into igt_hdr library Alex Hung
2026-03-17 17:51 ` [PATCH 2/3] tools: Add amd_hdr_visual for manual HDR verification Alex Hung
2026-03-18  9:52   ` Kamil Konieczny
2026-03-18 20:13     ` vitaly prosyak
2026-03-18 20:15       ` Alex Hung [this message]
2026-03-19  8:54   ` Jani Nikula
2026-03-17 17:51 ` [PATCH 3/3] lib/igt_hdr: Fix EOTF bit flag checking Alex Hung
2026-03-18  9:55   ` Kamil Konieczny
2026-03-18  0:50 ` ✓ Xe.CI.BAT: success for series starting with [1/3] lib/igt_hdr: Extract HDR helpers into igt_hdr library Patchwork
2026-03-18  1:04 ` ✓ i915.CI.BAT: " Patchwork
2026-03-18  7:34 ` [PATCH 1/3] " Sharma, Swati2
2026-03-18 18:40   ` Alex Hung
2026-03-18  9:30 ` Kamil Konieczny
2026-03-19 13:42 ` ✓ Xe.CI.FULL: success for series starting with [1/3] " Patchwork

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=9e09a519-b39a-4744-9718-4a05e68a2203@amd.com \
    --to=alex.hung@amd.com \
    --cc=Mark.Broadworth@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=vitaly.prosyak@amd.com \
    --cc=vprosyak@amd.com \
    --cc=wayne.lin@amd.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