From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: petri.latvala@intel.com
Cc: igt-dev@lists.freedesktop.org, nidhi1.gupta@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] Fix IGT Warnings due to dynamic subtest inclusion
Date: Mon, 09 Nov 2020 21:16:01 -0800 [thread overview]
Message-ID: <87wnytg5bi.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20201110045510.14716-1-nidhi1.gupta@intel.com>
On Mon, 09 Nov 2020 20:55:10 -0800, <nidhi1.gupta@intel.com> wrote:
>
> From: Nidhi Gupta <nidhi1.gupta@intel.com>
>
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
> ---
> tests/kms_atomic_interruptible.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/tests/kms_atomic_interruptible.c b/tests/kms_atomic_interruptible.c
> index 27bb6a2b..f98023ca 100644
> --- a/tests/kms_atomic_interruptible.c
> +++ b/tests/kms_atomic_interruptible.c
> @@ -288,7 +288,9 @@ igt_main
> for_each_pipe_with_valid_output(&display, pipe, output) {
> igt_dynamic_f("%s-pipe-%s", igt_output_name(output), kmstest_pipe_name(pipe))
> run_plane_test(&display, pipe, output, test_legacy_modeset, DRM_PLANE_TYPE_PRIMARY);
> + {
> break;
> + }
> }
Are we trying to break after the first call to run_plane_test() here? In
that case why are we using a for loop (for_each_pipe_with_valid_output)? I
am not sure if igt_subtest_with_dynamic/igt_dynamic_f combinations can take
a break statement, this code pattern is certainly not used elsewhere.
So the patch does fix the warnings (which is a relief) but otherwise I
don't know if it makes sense. If not, I'd say revert the previous patch and
do it a different way.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-11-10 5:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 4:55 [igt-dev] [PATCH i-g-t] Fix IGT Warnings due to dynamic subtest inclusion nidhi1.gupta
2020-11-10 5:16 ` Dixit, Ashutosh [this message]
2020-11-10 5:36 ` Zbigniew Kempczyński
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=87wnytg5bi.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=nidhi1.gupta@intel.com \
--cc=petri.latvala@intel.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