From: "Li, Juston" <juston.li@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ciobanu, Nathan D" <nathan.d.ciobanu@intel.com>,
"jared_dominguez@dell.com" <jared_dominguez@dell.com>,
"mario.limonciello@dell.com" <mario.limonciello@dell.com>
Subject: Re: [Intel-gfx] [RESEND PATCH v2 0/2] Check MST topology change on resume
Date: Wed, 24 Oct 2018 16:37:42 +0000 [thread overview]
Message-ID: <bdc963d6604f1ae7ff7c103c8d16b25db749a3e3.camel@intel.com> (raw)
In-Reply-To: <20181024085750.GK324@phenom.ffwll.local>
On Wed, 2018-10-24 at 10:57 +0200, Daniel Vetter wrote:
> On Tue, Oct 23, 2018 at 07:19:23PM -0700, Juston Li wrote:
> >
> > Signed-off-by: Juston Li <juston.li@intel.com>
>
> For formality, does this also imply a reviewed-by tag?
I'm quite new to drm so I'll withhold a reviewed-by tag and ask that
someone else take a look at it too.
Lyude, the original author, mentioned he should probably take a look
again also since the patchset is a bit old.
> For merging propably best we wait for the backmerge and the push
> these in
> through drm-misc-next-fixes.
>
> Well for drm-misc-next-fixes drm-misc maintainers need to roll the
> tree
> forward. Either way needs synchronization. Plus an ack from drm-intel
> maintainers.
> -Daniel
>
Will do
Thanks
Juston
prev parent reply other threads:[~2018-10-24 16:37 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
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 [this message]
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=bdc963d6604f1ae7ff7c103c8d16b25db749a3e3.camel@intel.com \
--to=juston.li@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jared_dominguez@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=nathan.d.ciobanu@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