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  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, 5 Oct 2021 14:14:59 +0100
From:   Lee Jones <>
To:     Mark Brown <>
Cc:     Krzysztof Kozlowski <>,
        Michael Turquette <>,
        Stephen Boyd <>,
        Rob Herring <>,
        Bartlomiej Zolnierkiewicz <>,
        Sylwester Nawrocki <>,
        Tomasz Figa <>,
        Chanwoo Choi <>,
        Liam Girdwood <>,,,,
Subject: Re: [PATCH v2 00/10] regulator/mfd/clock: dt-bindings: Samsung S2M
 and S5M to dtschema

On Tue, 05 Oct 2021, Mark Brown wrote:

> On Fri, Oct 01, 2021 at 11:40:56AM +0200, Krzysztof Kozlowski wrote:
> > Merging/dependencies
> > ====================
> > 1. Regulator related binding changes depend on first two commits (the
> >    fixes), because of context.
> > 2. The mfd bindings depend on clock and regulator bindings.
> > 
> > The fixes and bindings changes (patches 1-10) should go via the same
> > tree.  For example regulator or mfd tree.  I propose the regulator tree,
> > since it will have also one driver change (the fix, first commit).
> Lee, Stephen, Michael does Krzysztof's plan make sense to you?

I tend to take cross subsystem patches.  MFD is usually in the centre
of these scenarios and I have tooling to easily set-up immutable

Always happy to discuss if others have different/better ideas though.

Lee Jones [李琼斯]
Senior Technical Lead - Developer Services │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

Powered by blists - more mailing lists