Message ID | 20190903181256.13450-1-wsa+renesas@sang-engineering.com (mailing list archive) |
---|---|
Headers | show |
Series | hwmon: convert remaining drivers to i2c_new_dummy_device() | expand |
On Tue, Sep 03, 2019 at 08:12:53PM +0200, Wolfram Sang wrote: > This series is part of a tree-wide movement to replace the I2C API call > 'i2c_new_dummy' which returns NULL with its new counterpart returning an > ERRPTR. > > This series fixes the remaining hwmon drivers which could not be > converted by my cocci script. So, I did it manually, yet all drivers > still follow the same pattern. Build tested by me and by buildbot. No > tests on HW have been performed, so testing is appreciated. > I still have the previous version (with RFT) in my queue. Question is what to do with it; I have not seen any test feedback. I tend to just apply the series and wait for fallout. Any objections ? Guenter
On Tue, Sep 03, 2019 at 11:33:40AM -0700, Guenter Roeck wrote: > On Tue, Sep 03, 2019 at 08:12:53PM +0200, Wolfram Sang wrote: > > This series is part of a tree-wide movement to replace the I2C API call > > 'i2c_new_dummy' which returns NULL with its new counterpart returning an > > ERRPTR. > > > > This series fixes the remaining hwmon drivers which could not be > > converted by my cocci script. So, I did it manually, yet all drivers > > still follow the same pattern. Build tested by me and by buildbot. No > > tests on HW have been performed, so testing is appreciated. > > > I still have the previous version (with RFT) in my queue. > Question is what to do with it; I have not seen any test feedback. > I tend to just apply the series and wait for fallout. > Any objections ? For the sake of the API conversion, I would appreciate this much. Of course, I'll be there if there is fallout. Thanks!