From: Max Staudt <max@enpas.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 02/12] i2c: icy: convert to i2c_new_scanned_device
Date: Wed, 6 Nov 2019 12:33:30 +0100 [thread overview]
Message-ID: <6c979da5-d913-e2d9-9766-478a50d905f7@enpas.org> (raw)
In-Reply-To: <20191106095033.25182-3-wsa+renesas@sang-engineering.com>
On 11/06/2019 10:50 AM, Wolfram Sang wrote:
> Move from the deprecated i2c_new_probed_device() to the new
> i2c_new_scanned_device(). Make use of the new ERRPTR if suitable.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> drivers/i2c/busses/i2c-icy.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-icy.c b/drivers/i2c/busses/i2c-icy.c
> index 8382eb64b424..07baa4d8de39 100644
> --- a/drivers/i2c/busses/i2c-icy.c
> +++ b/drivers/i2c/busses/i2c-icy.c
> @@ -188,10 +188,10 @@ static int icy_probe(struct zorro_dev *z,
> ltc2990_info.fwnode = new_fwnode;
>
> i2c->ltc2990_client =
> - i2c_new_probed_device(&i2c->adapter,
> - <c2990_info,
> - icy_ltc2990_addresses,
> - NULL);
> + i2c_new_scanned_device(&i2c->adapter,
> + <c2990_info,
> + icy_ltc2990_addresses,
> + NULL);
Looks good, thank you for patching this!
i2c_unregister_device() checks the pointer using IS_ERR_OR_NULL(), so the simple logic in i2c-icy (where the pointer is not checked on i2c_new_scanned_device()) still works.
Acked-by: Max Staudt <max@enpas.org>
next prev parent reply other threads:[~2019-11-06 11:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:50 [RFC PATCH 00/12] i2c: replace i2c_new_probed_device with an ERR_PTR variant Wolfram Sang
2019-11-06 9:50 ` [RFC PATCH 01/12] " Wolfram Sang
2019-11-06 12:39 ` Max Staudt
2019-11-07 17:31 ` Luca Ceresoli
2019-11-07 19:22 ` Wolfram Sang
2019-11-08 8:01 ` Luca Ceresoli
2019-11-28 16:16 ` Wolfram Sang
2019-11-06 9:50 ` [RFC PATCH 02/12] i2c: icy: convert to i2c_new_scanned_device Wolfram Sang
2019-11-06 11:33 ` Max Staudt [this message]
2019-11-28 16:16 ` Wolfram Sang
2019-11-06 9:50 ` [RFC PATCH 03/12] macintosh: " Wolfram Sang
2019-11-06 9:50 ` [RFC PATCH 04/12] platform: chrome: " Wolfram Sang
2019-11-06 9:50 ` [RFC PATCH 05/12] video: fbdev: matrox: " Wolfram Sang
2019-11-07 8:33 ` Daniel Vetter
2019-11-28 16:18 ` Wolfram Sang
2019-11-28 16:19 ` Wolfram Sang
2019-11-06 9:50 ` [RFC PATCH 06/12] input: mouse: " Wolfram Sang
2019-11-11 18:19 ` Dmitry Torokhov
2019-11-06 9:50 ` [RFC PATCH 07/12] media: pci: cx23885: " Wolfram Sang
2019-11-06 11:18 ` Hans Verkuil
2019-11-06 9:50 ` [RFC PATCH 08/12] media: pci: cx88: " Wolfram Sang
2019-11-06 11:18 ` Hans Verkuil
2019-11-06 14:49 ` Wolfram Sang
2019-11-06 9:50 ` [RFC PATCH 09/12] media: pci: bt8xx: " Wolfram Sang
2019-11-06 11:19 ` Hans Verkuil
2019-11-06 9:50 ` [RFC PATCH 10/12] media: pci: cx18: " Wolfram Sang
2019-11-06 11:23 ` Hans Verkuil
2019-11-06 9:50 ` [RFC PATCH 11/12] media: pci: ivtv: " Wolfram Sang
2019-11-06 11:21 ` Hans Verkuil
2019-11-06 9:50 ` [RFC PATCH 12/12] media: v4l2-core: " Wolfram Sang
2019-11-06 11:24 ` Hans Verkuil
2019-11-06 10:06 ` [RFC PATCH 00/12] i2c: replace i2c_new_probed_device with an ERR_PTR variant Sean Young
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=6c979da5-d913-e2d9-9766-478a50d905f7@enpas.org \
--to=max@enpas.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
all inboxes | Powered by JetHome®