linux-kernel - Re: [PATCH v7 2/8] mfd: wm97xx-core: core support for wm97xx Codec

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 linux-hardening linux-cve-announce 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:   Tue, 19 Sep 2017 16:23:49 +0100
From:   Lee Jones <lee.jones@...aro.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Robert Jarzmik <robert.jarzmik@...e.fr>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Daniel Mack <daniel@...que.org>,
        Haojian Zhuang <haojian.zhuang@...il.com>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>,
        linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
        patches@...nsource.wolfsonmicro.com, alsa-devel@...a-project.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v7 2/8] mfd: wm97xx-core: core support for wm97xx Codec

On Tue, 19 Sep 2017, Lee Jones wrote:

> On Tue, 19 Sep 2017, Mark Brown wrote:
> 
> > On Mon, Sep 18, 2017 at 09:52:36AM +0100, Lee Jones wrote:
> > > On Thu, 14 Sep 2017, Mark Brown wrote:
> > 
> > > > On Thu, Sep 14, 2017 at 08:43:00AM +0100, Lee Jones wrote:
> > 
> > > > > Change of plan.  It looks like there are deps.
> > 
> > > > > Unapplied.
> > 
> > > > The core stuff went in during the merge window, you should be able to
> > > > wait for -rc1 or pick up the asoc-v4.14 tag.
> > 
> > > No, I mean patches; 3, 4, 5 and 7 depend on this file.
> > 
> > Right, but I'd have expected a pull request more than the patch being
> > unapplied?
> 
> Normally I wait until all patches patches in the set have been
> reviewed (the ASOC ones still have not), then ask the OP and the
> other affected Maintainers how they want to deal with the patch.
> Far more often than not, the the solution is just to take the set
> through the MFD tree.
> 
> However, since this is a new driver, you can just take it with my:
> 
> Acked-by: Lee Jones <lee.jones@...aro.org>

... although that does mean that you'll have to handle one of the
Input patches too.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog