[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190219123530.GA4626@kroah.com>
Date: Tue, 19 Feb 2019 13:35:30 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Arnd Bergmann <arnd@...db.de>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
dri-devel@...ts.freedesktop.org, intel-gfx@...ts.freedesktop.org,
dim-tools@...ts.freedesktop.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PULL] topic/mei-hdcp
On Tue, Feb 19, 2019 at 08:55:27AM +0100, Daniel Vetter wrote:
> Hi all,
>
> topic/mei-hdcp-2019-02-19:
> Prep patches + headers for the mei-hdcp/i915 component interfaces
>
> Also contains the prep work in the component helpers plus adjustements
> for the snd-hda/i915 component interface.
>
> Plus one small static inline in the drm_hdcp.h header that both i915
> and mei_hdcp will need.
>
> Joonas, please pull into drm-intel-next-queued so I can apply the i915
> hdcp patches.
>
> Greg/Arnd, I think there's two options to get the mei-hdcp patches landed
> into drivers-misc:
> - You pull this topic pull and then apply the mei-hdcp patches on top in
> char-misc-next.
> - I also pull in char-misc-next to get at 32ea33a04484 ("mei: bus: export
> to_mei_cl_device for mei client devices drivers") and then apply all the
> mei-hdcp stuff into a new topic branch.
>
> I think 2nd option would be better, allows us to integration test easier,
> and we'll have a topic branch in case we need a fixup spanning mei-hdcp
> and i915. Also would allow me to start merging the patches, since I think
> it's too late for 5.1.
No objection from me, pull away!
greg k-h
Powered by blists - more mailing lists