From: "Li, Juston" <juston.li@intel.com>
To: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"lyude@redhat.com" <lyude@redhat.com>
Cc: "Ciobanu, Nathan D" <nathan.d.ciobanu@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Taylor, Clinton A" <clinton.a.taylor@intel.com>,
"jared_dominguez@dell.com" <jared_dominguez@dell.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"mario.limonciello@dell.com" <mario.limonciello@dell.com>,
"cpaul@redhat.com" <cpaul@redhat.com>
Subject: Re: [RESEND PATCH v2 1/2] drm/dp/mst: Reprobe EDID for MST ports on resume
Date: Wed, 24 Oct 2018 22:45:54 +0000 [thread overview]
Message-ID: <ee20a313fb63792c05ab1b67babf1fa9431ebcf8.camel@intel.com> (raw)
In-Reply-To: <f9b43dde4868d3c079b652b48babde9b8bebc728.camel@redhat.com>
On Wed, 2018-10-24 at 18:09 -0400, Lyude Paul wrote:
> Since there's going to be quite a number of changes I need to make to
> this I'm
> just going to make the changes myself! I'll make sure to Cc you with
> the
> respin
Sounds good, thanks for picking it up!
Juston
next prev parent reply other threads:[~2018-10-24 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 2:19 [RESEND PATCH v2 0/2] Check MST topology change on resume Juston Li
2018-10-24 2:19 ` [RESEND PATCH v2 1/2] drm/dp/mst: Reprobe EDID for MST ports " Juston Li
2018-10-24 22:09 ` Lyude Paul
2018-10-24 22:45 ` Li, Juston [this message]
2018-11-09 0:43 ` Lyude Paul
2018-11-26 21:53 ` Li, Juston
2018-11-26 22:35 ` Lyude Paul
2018-10-24 23:02 ` Lyude Paul
2018-10-24 2:19 ` [RESEND PATCH v2 2/2] drm/i915/mst: Reset MST after resume when necessary Juston Li
2018-10-24 8:57 ` [Intel-gfx] [RESEND PATCH v2 0/2] Check MST topology change on resume Daniel Vetter
2018-10-24 16:37 ` Li, Juston
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=ee20a313fb63792c05ab1b67babf1fa9431ebcf8.camel@intel.com \
--to=juston.li@intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=cpaul@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jared_dominguez@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mario.limonciello@dell.com \
--cc=nathan.d.ciobanu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).