From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Takashi Iwai <tiwai@suse.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <sean@poorly.run>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@gmail.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"DRM maintainer tools announcements, discussion,
and development" <dim-tools@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PULL] topic/component-typed
Date: Tue, 12 Feb 2019 10:24:17 +0100 [thread overview]
Message-ID: <20190212092417.rs4alnres4he5nvx@flea> (raw)
In-Reply-To: <CAKMK7uHU37VLbe4RBZ3GOow+=pupYAHotkVrpqJeiUcpSfjX8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
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.
> Probably good if you pull this into drivers-core so it lands a bit
> quicker. You&Arnd will also get a topic pull later on with the MEI bits
> for char-misc tree, which needs to be based on top of this tree here.
>
> Takashi: Since the drm side only lands in 5.2 might be good if you
> pull this in too to avoid conflicts.
>
> Cheers, Daniel
Pulled into drm-misc, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2019-02-12 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 17:15 [PULL] topic/component-typed Daniel Vetter
2019-02-11 18:25 ` Sam Ravnborg
2019-02-11 18:50 ` Daniel Vetter
2019-02-11 18:57 ` Takashi Iwai
2019-02-11 19:18 ` Daniel Vetter
2019-02-11 19:34 ` Greg KH
2019-02-12 9:24 ` Maxime Ripard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190212092417.rs4alnres4he5nvx@flea \
--to=maxime.ripard@bootlin.com \
--cc=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).