From: Takashi Iwai <tiwai@suse.de>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"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>, <tiwai@suse.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PULL] topic/component-typed
Date: Mon, 11 Feb 2019 19:57:07 +0100 [thread overview]
Message-ID: <s5ho97idugs.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190211182512.GA28363@ravnborg.org>
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.
thanks,
Takashi
next prev parent reply other threads:[~2019-02-11 18:57 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 [this message]
2019-02-11 19:18 ` Daniel Vetter
2019-02-11 19:34 ` Greg KH
2019-02-12 9:24 ` Maxime Ripard
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=s5ho97idugs.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--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=maxime.ripard@bootlin.com \
--cc=rodrigo.vivi@intel.com \
--cc=sam@ravnborg.org \
--cc=sean@poorly.run \
/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).