linux-kernel - Re: [PATCH 1/2] Add sw2_sw4 voltage table to cpcap regulator.

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]

Date:   Mon, 23 Jul 2018 14:37:50 -0400
From:   Peter Geis <pgwipeout@...il.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     lgirdwood@...il.com, robh+dt@...nel.org, mark.rutland@....com,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        linux-tegra@...r.kernel.org
Subject: Re: [PATCH 1/2] Add sw2_sw4 voltage table to cpcap regulator.

On 07/23/2018 02:13 PM, Mark Brown wrote:
> On Mon, Jul 23, 2018 at 01:58:26PM -0400, Peter Geis wrote:
>> SW2 and SW4 use a shared table to provide voltage to the cpu core and
>> devices on Tegra hardware.
>> Added this table to the cpcap regulator driver as the first step to
>> supporting this device on Tegra.
> 
> This also doesn't apply against current code (though it does now parse
> OK), please check and resend - make sure you don't have other out of
> tree changes and are using an up to date kernel (ideally my regulator
> for-next branch) as a base.
> 
Good Afternoon,

I thought it was my error in the patches being stripped, unfortunately 
it seems to be a known Gmail behavior.
Any ideas on how to get around it?

Thanks,
Peter