From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_dp_dsc: Disable DSC even if enabling failed
Date: Mon, 25 Mar 2019 11:17:54 -0700 [thread overview]
Message-ID: <56bc5185c41b0f9acc00e310c3bcaaff8e21356e.camel@intel.com> (raw)
In-Reply-To: <27039e7645410bbb1804454df624bf3a22911deb.camel@intel.com>
On Fri, 2019-03-22 at 13:33 -0700, Souza, Jose wrote:
> On Thu, 2019-03-21 at 16:18 -0700, Dhinakaran Pandiyan wrote:
> > The test leaves the debugfs flag enabled if the driver failed to
> > enable
> > DSC. And is it turns out, the feature gets enabled only after the
> > test
> > completes and consequently affects PSR2 tests that follow. Let's make
> > sure
> > the test cleans up correctly, even if the DSC test itself needs to be
> > fixed.
> >
> > Also included some formatting fixes within the function.
>
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
Pushed, thanks!
-DK
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-25 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 23:18 [igt-dev] [PATCH i-g-t] tests/kms_dp_dsc: Disable DSC even if enabling failed Dhinakaran Pandiyan
2019-03-21 23:50 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-03-22 19:02 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_dp_dsc: Disable DSC even if enabling failed (rev2) Patchwork
2019-03-22 20:33 ` [igt-dev] [PATCH i-g-t] tests/kms_dp_dsc: Disable DSC even if enabling failed Souza, Jose
2019-03-25 18:17 ` Dhinakaran Pandiyan [this message]
2019-03-23 18:25 ` [igt-dev] ✓ Fi.CI.IGT: success for tests/kms_dp_dsc: Disable DSC even if enabling failed (rev2) 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=56bc5185c41b0f9acc00e310c3bcaaff8e21356e.camel@intel.com \
--to=dhinakaran.pandiyan@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jose.souza@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