linux-kernel - Re: [PATCH V4 2/5] regulator: make regulator voltage be an array to support more states

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: <20180123160459.GH7600@sirena.org.uk>
Date:   Tue, 23 Jan 2018 16:04:59 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Chunyan Zhang <zhang.chunyan@...aro.org>
Cc:     Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Chunyan Zhang <zhang.lyra@...il.com>
Subject: Re: [PATCH V4 2/5] regulator: make regulator voltage be an array to
 support more states

On Tue, Jan 23, 2018 at 07:59:40PM +0800, Chunyan Zhang wrote:
> Some regulator consumers would like to make the regulator device
> keeping a voltage range output when the system entering into
> suspend states.

I tried to apply these but there's earlier versions of some of them
already applied on my topic/suspend branch so it's just a world of
conflicts - can you please rebase against that branch (or my for-next)?

Please don't resubmit patches that have already been applied, you should
submit patches against current code in the tree you're expecting things
to be applied to.  If any updates are needed to a patch that's already
been applied you should submit incremental patches which make those
updates.  This avoids having to change published git commits which could
cause problems for people working against git.

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