From: "B, Jeevan" <jeevan.b@intel.com>
To: "Joshi, Kunal1" <kunal1.joshi@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Joshi, Kunal1" <kunal1.joshi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v1 4/5] tests/kms_invalid_mode.c
Date: Tue, 27 Sep 2022 08:54:32 +0000 [thread overview]
Message-ID: <DM4PR11MB6312EC4D066E83AC30010DDA90559@DM4PR11MB6312.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220926185321.2897136-5-kunal1.joshi@intel.com>
> -----Original Message-----
> From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Kunal
> Joshi
> Sent: Tuesday, September 27, 2022 12:23 AM
> To: igt-dev@lists.freedesktop.org
> Cc: Joshi, Kunal1 <kunal1.joshi@intel.com>
Hi Kunal,
Correct subject.
Thanks
Jeevan B
> Subject: [igt-dev] [PATCH i-g-t v1 4/5] tests/kms_invalid_mode.c
>
> -> close drm_fd
>
> Cc: Karthik B S <karthik.b.s@intel.com>
> Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
> ---
> tests/kms_invalid_mode.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/kms_invalid_mode.c b/tests/kms_invalid_mode.c index
> 0ae98a31..f1c38669 100644
> --- a/tests/kms_invalid_mode.c
> +++ b/tests/kms_invalid_mode.c
> @@ -306,5 +306,6 @@ igt_main
> igt_fixture {
> igt_display_fini(&data.display);
> igt_reset_connectors();
> + close(data.drm_fd);
> }
> }
> --
> 2.25.1
next prev parent reply other threads:[~2022-09-27 8:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:53 [igt-dev] [PATCH i-g-t v1 0/5] IGT test cleanup Kunal Joshi
2022-09-26 18:53 ` [igt-dev] [PATCH i-g-t v1 1/5] tests/chamelium/kms_chamelium.c: " Kunal Joshi
2022-09-27 8:58 ` B, Jeevan
2022-09-27 13:50 ` Swati Sharma
2022-09-26 18:53 ` [igt-dev] [PATCH i-g-t v1 2/5] tests/i915/kms_pipe_b_c_ivb.c: " Kunal Joshi
2022-09-27 2:45 ` B, Jeevan
2022-09-27 8:26 ` Joshi, Kunal1
2022-09-27 8:34 ` B, Jeevan
2022-09-27 13:53 ` Swati Sharma
2022-09-26 18:53 ` [igt-dev] [PATCH i-g-t v1 3/5] tests/i915/kms_pwrite_crc.c: cleanup Kunal Joshi
2022-09-27 8:56 ` B, Jeevan
2022-09-27 13:57 ` Swati Sharma
2022-09-26 18:53 ` [igt-dev] [PATCH i-g-t v1 4/5] tests/kms_invalid_mode.c Kunal Joshi
2022-09-27 8:54 ` B, Jeevan [this message]
2022-09-27 13:59 ` Swati Sharma
2022-09-26 18:53 ` [igt-dev] [PATCH i-g-t v1 5/5] tests/kms_hdmi_inject: test cleanup Kunal Joshi
2022-09-27 8:51 ` B, Jeevan
2022-09-27 14:00 ` Swati Sharma
2022-09-26 19:23 ` [igt-dev] ✗ GitLab.Pipeline: warning for IGT " Patchwork
2022-09-26 19:47 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-09-27 3:51 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=DM4PR11MB6312EC4D066E83AC30010DDA90559@DM4PR11MB6312.namprd11.prod.outlook.com \
--to=jeevan.b@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kunal1.joshi@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 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.