[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bdc963d6604f1ae7ff7c103c8d16b25db749a3e3.camel@intel.com>
Date: Wed, 24 Oct 2018 16:37:42 +0000
From: "Li, Juston" <juston.li@...el.com>
To: "daniel@...ll.ch" <daniel@...ll.ch>
CC: "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Ciobanu, Nathan D" <nathan.d.ciobanu@...el.com>,
"jared_dominguez@...l.com" <jared_dominguez@...l.com>,
"mario.limonciello@...l.com" <mario.limonciello@...l.com>
Subject: Re: [Intel-gfx] [RESEND PATCH v2 0/2] Check MST topology change on
resume
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@...el.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
Powered by blists - more mailing lists