lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 11 Feb 2019 19:57:07 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     "Sam Ravnborg" <sam@...nborg.org>
Cc:     "Daniel Vetter" <daniel.vetter@...ll.ch>,
        "Arnd Bergmann" <arnd@...db.de>,
        "Maxime Ripard" <maxime.ripard@...tlin.com>,
        "Rodrigo Vivi" <rodrigo.vivi@...el.com>,
        "Jani Nikula" <jani.nikula@...ux.intel.com>,
        "Joonas Lahtinen" <joonas.lahtinen@...ux.intel.com>,
        "Maarten Lankhorst" <maarten.lankhorst@...ux.intel.com>,
        "Greg KH" <gregkh@...uxfoundation.org>,
        "discussion and development DRM maintainer tools announcements" 
        <dim-tools@...ts.freedesktop.org>,
        "dri-devel" <dri-devel@...ts.freedesktop.org>,
        "intel-gfx" <intel-gfx@...ts.freedesktop.org>,
        "Sean Paul" <sean@...rly.run>, <tiwai@...e.de>,
        "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PULL] topic/component-typed

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

Powered by blists - more mailing lists