[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKMK7uENU2dc6eKqzTYwNs=4uAVhDv1GSA1KpuAEB8ZANCsS1A@mail.gmail.com>
Date: Mon, 11 Feb 2019 19:50:21 +0100
From: Daniel Vetter <daniel.vetter@...ll.ch>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Takashi Iwai <tiwai@...e.com>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Arnd Bergmann <arnd@...db.de>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Sean Paul <sean@...rly.run>,
Maxime Ripard <maxime.ripard@...tlin.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
"DRM maintainer tools announcements, discussion, and development"
<dim-tools@...ts.freedesktop.org>,
intel-gfx <intel-gfx@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [PULL] topic/component-typed
On Mon, Feb 11, 2019 at 7:25 PM Sam Ravnborg <sam@...nborg.org> wrote:
>
> Hi Daniel.
>
> On Mon, Feb 11, 2019 at 06:15:20PM +0100, Daniel Vetter wrote:
> > Hi all,
> >
> > Here's the typed component topic branch.
> >
> > drm-intel maintainers: Please pull, I need this for the mei hdcp work from Ram.
> >
> > drm-misc maintainers: Please pull, there's a drm doc patch follow-up
> > that I want to stuff into drm-misc-next.
> >
> > Greg: The drm side missed our feature cutoff, so will only land in 5.2.
>
> With all the dependencies why not bend the rule a little and get this in now?
> It is not like this is a huge patchset.
The feature that depends upon this is almost 40 patches. That's a bit
much for bending :-) Hence why I'm asking Greg to pull this, so it's
not stuck out of tree for 3 months for no good reason.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
Powered by blists - more mailing lists