From: Guenter Roeck <linux@roeck-us.net>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/3] hwmon: convert remaining drivers to i2c_new_dummy_device()
Date: Tue, 3 Sep 2019 11:33:40 -0700 [thread overview]
Message-ID: <20190903183340.GA29077@roeck-us.net> (raw)
In-Reply-To: <20190903181256.13450-1-wsa+renesas@sang-engineering.com>
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
next prev parent reply other threads:[~2019-09-03 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 18:12 [PATCH RESEND 0/3] hwmon: convert remaining drivers to i2c_new_dummy_device() Wolfram Sang
2019-09-03 18:12 ` [PATCH RESEND 1/3] hwmon: w83791d: convert to use devm_i2c_new_dummy_device Wolfram Sang
2019-09-03 19:44 ` Guenter Roeck
2019-09-03 18:12 ` [PATCH RESEND 2/3] hwmon: w83792d: " Wolfram Sang
2019-09-03 19:45 ` Guenter Roeck
2019-09-03 18:12 ` [PATCH RESEND 3/3] hwmon: w83793d: " Wolfram Sang
2019-09-03 19:46 ` Guenter Roeck
2019-09-03 18:33 ` Guenter Roeck [this message]
2019-09-03 18:37 ` [PATCH RESEND 0/3] hwmon: convert remaining drivers to i2c_new_dummy_device() Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190903183340.GA29077@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).