Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAKMK7uHU37VLbe4RBZ3GOow+=pupYAHotkVrpqJeiUcpSfjX8Q@mail.gmail.com>
 <20190211182512.GA28363@ravnborg.org> <s5ho97idugs.wl-tiwai@suse.de>
In-Reply-To: <s5ho97idugs.wl-tiwai@suse.de>
From:   Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Mon, 11 Feb 2019 20:18:04 +0100
Message-ID: <CAKMK7uGuJZiQZ2hSwod5VwT69FVhR6HeREc07Bx3QD=a3QQ=Gw@mail.gmail.com>
Subject: Re: [PULL] topic/component-typed
To:     Takashi Iwai <tiwai@suse.de>
Cc:     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>,
        Greg KH <gregkh@linuxfoundation.org>,
        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>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch