linux-kernel - Re: [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after reset

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]

Date:   Mon, 14 Sep 2020 20:50:26 +0000
From:   Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To:     Wolfram Sang <wsa@...nel.org>
CC:     Evan Nimmo <Evan.Nimmo@...iedtelesis.co.nz>,
        "andriy.shevchenko@...ux.intel.com" 
        <andriy.shevchenko@...ux.intel.com>,
        "jarkko.nikula@...ux.intel.com" <jarkko.nikula@...ux.intel.com>,
        "jdelvare@...e.de" <jdelvare@...e.de>,
        "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after
 reset


On 14/09/20 6:49 pm, Wolfram Sang wrote:
>> I'm happy to route it to stable@ if you think it's worth it but I don't
>> think there's a specific Fixes: reference that can be used. The current
>> behavior appears to have been that way since before git (looks like we
>> noticed in 2014 but it's taken me 6 years to nag people into sending
>> their fixes upstream).
> Better late than never :) Thanks for sending and the heads up. If you
> don't need it for stable, then we should maybe not send it. It would be
> nice for 9665 but we haven't tested it on 9564. But I'll let it be your
> call.
>
Looks like it's been picked up already. If anyone does hit problems on 
the 9564 hopefully the interweb will lead them to this mailing list 
thread and they'll have some people to hassle.