From mboxrd@z Thu Jan  1 00:00:00 1970
From: Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PULL] topic/component-typed
Date: Mon, 11 Feb 2019 20:34:25 +0100
Message-ID: <20190211193425.GA22535@kroah.com>
References: <CAKMK7uHU37VLbe4RBZ3GOow+=pupYAHotkVrpqJeiUcpSfjX8Q@mail.gmail.com>
 <20190211182512.GA28363@ravnborg.org>
 <s5ho97idugs.wl-tiwai@suse.de>
 <CAKMK7uGuJZiQZ2hSwod5VwT69FVhR6HeREc07Bx3QD=a3QQ=Gw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <CAKMK7uGuJZiQZ2hSwod5VwT69FVhR6HeREc07Bx3QD=a3QQ=Gw@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Takashi Iwai <tiwai@suse.de>, Sam Ravnborg <sam@ravnborg.org>, Arnd Bergmann <arnd@arndb.de>, Maxime Ripard <maxime.ripard@bootlin.com>, Rodrigo Vivi <rodrigo.vivi@intel.com>, Jani Nikula <jani.nikula@linux.intel.com>, Joonas Lahtinen <joonas.lahtinen@linux.intel.com>, Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, discussion and development DRM maintainer tools announcements <dim-tools@lists.freedesktop.org>, dri-devel <dri-devel@lists.freedesktop.org>, intel-gfx <intel-gfx@lists.freedesktop.org>, Sean Paul <sean@poorly.run>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
List-Id: dri-devel@lists.freedesktop.org

On Mon, Feb 11, 2019 at 08:18:04PM +0100, Daniel Vetter wrote:
> On Mon, Feb 11, 2019 at 7:57 PM Takashi Iwai <tiwai@suse.de> wrote:
> >
> > On Mon, 11 Feb 2019 19:25:12 +0100,
> > Sam Ravnborg 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.
> >
> > Yeah, that's likely the most straightforward way.
> >
> > BTW, I tried to pull onto sound git tree for-next branch, and it
> > worked without conflicts.  So I don't think it needs to be pulled onto
> > mine.
> 
> Yeah right now it's all conflict free, I'm more worried about what's
> going to happen the next 3 months. That's also why I think it'd be
> good if Greg can pull this still.

Ok, I've pulled this into my branch, it should go into 5.1-rc1.

thanks,

greg k-h