linux-kernel - Re: [PATCH v2 0/2] check I2C device id for pca984x chips

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <7fdb753f-2330-e93c-bbe3-e59fd96a253d@axentia.se>
Date:   Sat, 10 Mar 2018 01:05:43 +0100
From:   Peter Rosin <peda@...ntia.se>
To:     linux-kernel@...r.kernel.org
Cc:     Wolfram Sang <wsa@...-dreams.de>,
        Adrian Fiergolski <adrian.fiergolski@...n.ch>,
        linux-i2c@...r.kernel.org
Subject: Re: [PATCH v2 0/2] check I2C device id for pca984x chips

On 2018-03-05 21:58, Peter Rosin wrote:
> Hi!
> 
> This series tries to check the I2C device id, but instead of open
> coding the check in the pca954x driver, I have a new function in
> the core doing the work.
> 
> Changes since v1:
> - Added Tested-by tag from Adrian
> - Added Reviewed-by tag from Wolfram
> - Replaced client->flags with a zero in the i2c_smbus_xfer call
> 
> Wolfram: I'll send a pull with the first patch in a few days, to
> allow for a second round of feedback now that the RFC marker is gone.

Both patches pushed to i2c-mux/for-next.

Cheers,
Peter