linux-kernel - Re: [PATCH v15 0/7] support ROHM BD70528 PMIC

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]

Message-ID: <20190619143112.GO23549@piout.net>
Date:   Wed, 19 Jun 2019 16:31:12 +0200
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     Sebastian Reichel <sre@...nel.org>
Cc:     Lee Jones <lee.jones@...aro.org>, mazziesaccount@...il.com,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>,
        Alessandro Zummo <a.zummo@...ertech.it>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-gpio@...r.kernel.org,
        linux-pm@...r.kernel.org, linux-rtc@...r.kernel.org
Subject: Re: [PATCH v15 0/7] support ROHM BD70528 PMIC

On 13/06/2019 15:05:29+0200, Sebastian Reichel wrote:
> Hi,
> 
> On Wed, Jun 12, 2019 at 07:03:28AM +0100, Lee Jones wrote:
> > On Tue, 11 Jun 2019, Sebastian Reichel wrote:
> > > On Mon, Jun 03, 2019 at 10:23:37AM +0300, Matti Vaittinen wrote:
> > > > Patch series introducing support for ROHM BD70528 PMIC
> > > > [...]
> > > 
> > > I think all patches have been reviewed by the respective subsystem
> > > maintainers. Lee, can you provide an immutable branch with the MFD
> > > patches (1, 2, 4)? Looks like the other patches only depend on those
> > > and can go through their respective subsystems.
> > 
> > Yes.  It's on my TODO list.
> 
> Thanks.
> 
> > Would you prefer this method over me just taking them all and sending
> > out a PR?  The latter is my usual flow, but I'm happy with either.
> 
> Both methods are fine with me. I usually go with "my" method, since
> that results in less shared commits. It simplifies potential
> follow-up bug fixes, since there is only one tree to fix.
> 

Personally, I'm fine with Lee taking everything in his tree as it is
very unlikely to require follow up patches this cycle (i.e before rc1).


-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com