linux-kernel - RE: [PATCH] mfd: da9063: occupy second I2C address, too

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]

Date:   Fri, 21 Jun 2019 10:23:26 +0000
From:   Steve Twiss <stwiss.opensource@...semi.com>
To:     Wolfram Sang <wsa@...-dreams.de>
CC:     "wsa+renesas@...g-engineering.com" <wsa+renesas@...g-engineering.com>,
        "bgolaszewski@...libre.com" <bgolaszewski@...libre.com>,
        "kieran.bingham+renesas@...asonboard.com" 
        <kieran.bingham+renesas@...asonboard.com>,
        "lee.jones@...aro.org" <lee.jones@...aro.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-renesas-soc@...r.kernel.org" 
        <linux-renesas-soc@...r.kernel.org>,
        "peda@...ntia.se" <peda@...ntia.se>,
        Support Opensource <Support.Opensource@...semi.com>
Subject: RE: [PATCH] mfd: da9063: occupy second I2C address, too

On 21 June 2019 11:10 Wolfram Sang wrote:

> Subject: Re: [PATCH] mfd: da9063: occupy second I2C address, too
> 
> > For what it's worth, maybe consider adding a dev_warn attached to the return
> > of devm_i2c_new_dummy_device?
> 
> I am in the middle of some API changes. Once those are over, I want to
> think about such warnings as a second step. I'd rather have them in the
> core than in each and every driver. But this needs more thinking...

No problem.