linux-kernel - Re: [PATCH v3 1/4] regulator: mp886x: implement set_ramp

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] [day] [month] [year] [list]

Message-ID: <20200821095724.GA4870@sirena.org.uk>
Date:   Fri, 21 Aug 2020 10:57:24 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Jisheng Zhang <Jisheng.Zhang@...aptics.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Saravanan Sekar <sravanhome@...il.com>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3 1/4] regulator: mp886x: implement set_ramp_delay

On Fri, Aug 21, 2020 at 10:17:29AM +0800, Jisheng Zhang wrote:

> I found the reason, the three patches in v2 were applied to for-next tree.
> Should I renew patches based on for-next? Since the "mps,switch-frequency"
> binding isn't released and used, I think I can send new patches to convert
> mps,switch-frequency to mps,switch-frequency-hz.

Yes, please - for-next is best for anything that isn't a bug fix.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)