From: Jani Nikula <jani.nikula@intel.com>
To: dhinakaran.pandiyan@intel.com, intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
"# v4 . 14+" <stable@vger.kernel.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] Revert "drm/i915/edp: Allow alternate fixed mode for eDP if available."
Date: Tue, 22 May 2018 12:44:16 +0300 [thread overview]
Message-ID: <87d0xovxcf.fsf@intel.com> (raw)
In-Reply-To: <1526586282.17473.177.camel@intel.com>
On Thu, 17 May 2018, Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com> wrote:
> Yeah, agreed on starting with a clean slate.
>
> The offending commit claims alternate mode was intended to be used for
> PSR testing. I don't see any psr_basic failures in BAT or any other PSR
> sub-tests failing on shards, must have been a non-CI machine then.
>
> The revert itself looks correct,
> Reviewed-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Thanks for the review, pushed to dinq.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2018-05-22 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 8:01 [PATCH] Revert "drm/i915/edp: Allow alternate fixed mode for eDP if available." Jani Nikula
2018-05-16 9:29 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-16 17:08 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-05-16 23:30 ` [Intel-gfx] [PATCH] " Dhinakaran Pandiyan
2018-05-17 7:19 ` Jani Nikula
2018-05-17 7:33 ` Jani Nikula
2018-05-17 7:33 ` [Intel-gfx] " Jani Nikula
2018-05-17 19:44 ` Dhinakaran Pandiyan
2018-05-18 19:53 ` Dhinakaran Pandiyan
2018-05-17 19:44 ` Dhinakaran Pandiyan
2018-05-17 19:44 ` [Intel-gfx] " Dhinakaran Pandiyan
2018-05-22 9:44 ` Jani Nikula [this message]
2018-05-18 7:19 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-18 8:10 ` ✗ 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=87d0xovxcf.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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.