linux-kernel - Re: [PATCH v3 01/17] mfd: madera: Add register definitions for Cirrus Logic Madera codecs

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:   Thu, 29 Jun 2017 10:11:34 +0100
From:   Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>
To:     Mark Brown <broonie@...nel.org>
CC:     Lee Jones <lee.jones@...aro.org>, <linus.walleij@...aro.org>,
        <gnurou@...il.com>, <robh+dt@...nel.org>, <tglx@...utronix.de>,
        <jason@...edaemon.net>, <alsa-devel@...a-project.org>,
        <patches@...nsource.wolfsonmicro.com>,
        <linux-gpio@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 01/17] mfd: madera: Add register definitions for
 Cirrus Logic Madera codecs

On Wed, 2017-06-28 at 20:26 +0100, Mark Brown wrote:
> On Mon, Jun 26, 2017 at 09:33:38AM +0100, Richard Fitzgerald wrote:
> > On Mon, 2017-06-05 at 11:07 +0100, Lee Jones wrote:
> 
> > > For my own reference:
> > >   Acked-for-MFD-by: Lee Jones <lee.jones@...aro.org>
> 
> > Can I suggest that you take this patch into the mfd tree? Other
> > subsystem maintainers will have to base on that but it avoids me keeping
> > emailing out nearly 9000 lines of register definitions each time I do an
> > update to the other patches in the chain.
> 
> Yes, please!  It also helps other maintainers see that the early bits of
> the series we depend on are making progress.

I guess taking all the MFD code when Lee is happy with it would also be
acceptable? There's several multi-thousand-line files in there too.

There are build dependencies between the subsystems but I don't know how
the maintainers prefer to deal with that - keep the patches as a set or
cross-merge branches.