linux-kernel - Re: [PATCH/RFC v2 3/3] regulator: fixed: Handle optional overcurrent pin

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: <20161104182000.gzkbfh4weyq74ubx@sirena.org.uk>
Date:   Fri, 4 Nov 2016 12:20:00 -0600
From:   Mark Brown <broonie@...nel.org>
To:     Axel Haslam <ahaslam@...libre.com>
Cc:     lgirdwood@...il.com, khilman@...libre.com, nsekhar@...com,
        david@...hnology.com, robh+dt@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH/RFC v2 3/3] regulator: fixed: Handle optional overcurrent
 pin

On Thu, Nov 03, 2016 at 12:11:44PM +0100, Axel Haslam wrote:
> Fixed regulators (ex. TPS2087D) may have a over current pin that
> is activated on over current. Consumers may be interested to know
> about over current events to take appropriate actions.

This doesn't apply against current code, please check and resend.

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