From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-fbdev@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-input@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-media@vger.kernel.org
Subject: [RFC PATCH 00/12] i2c: replace i2c_new_probed_device with an ERR_PTR variant
Date: Wed, 6 Nov 2019 10:50:18 +0100 [thread overview]
Message-ID: <20191106095033.25182-1-wsa+renesas@sang-engineering.com> (raw)
From: Wolfram Sang <wsa@the-dreams.de>
In the on-going mission to let i2c_new_* calls return an ERR_PTR instead
of NULL, here is a series converting i2c_new_probed_device(). A new
function called i2c_new_scanned_device() is introduced with the new
retval, but for now, a compatibility helper is provided until all users
are converted. The rest of the patches convert all current in-tree
users.
Note that these patches are RFC because I want feedback on the approach
and hopefully collect acks on the driver conversions. If all goes well,
I'll apply the first two patches for the next merge window. Then, once
this dependency is upstream, I'll resend this series with all issues
fixed and acks collected.
Core changes tested on a Renesas Salvator-XS board (R-Car M3-N), driver
patches build tested by me and buildbot.
Wolfram Sang (12):
i2c: replace i2c_new_probed_device with an ERR_PTR variant
i2c: icy: convert to i2c_new_scanned_device
macintosh: convert to i2c_new_scanned_device
platform: chrome: convert to i2c_new_scanned_device
video: fbdev: matrox: convert to i2c_new_scanned_device
input: mouse: convert to i2c_new_scanned_device
media: pci: cx23885: convert to i2c_new_scanned_device
media: pci: cx88: convert to i2c_new_scanned_device
media: pci: bt8xx: convert to i2c_new_scanned_device
media: pci: cx18: convert to i2c_new_scanned_device
media: pci: ivtv: convert to i2c_new_scanned_device
media: v4l2-core: convert to i2c_new_scanned_device
Documentation/i2c/instantiating-devices.rst | 10 ++++-----
Documentation/i2c/writing-clients.rst | 8 +++----
drivers/i2c/busses/i2c-icy.c | 8 +++----
drivers/i2c/i2c-core-base.c | 25 ++++++++++++++++-----
drivers/input/mouse/psmouse-smbus.c | 8 ++++---
drivers/macintosh/therm_windtunnel.c | 4 ++--
drivers/media/pci/bt8xx/bttv-input.c | 6 ++---
drivers/media/pci/cx18/cx18-i2c.c | 2 +-
drivers/media/pci/cx23885/cx23885-i2c.c | 4 ++--
drivers/media/pci/cx88/cx88-input.c | 2 +-
drivers/media/pci/ivtv/ivtv-i2c.c | 6 ++---
drivers/media/pci/ivtv/ivtv-i2c.h | 2 +-
drivers/media/v4l2-core/v4l2-i2c.c | 10 ++++-----
drivers/platform/chrome/chromeos_laptop.c | 18 ++++++++-------
drivers/video/fbdev/matrox/i2c-matroxfb.c | 4 ++--
include/linux/i2c.h | 12 +++++++---
16 files changed, 76 insertions(+), 53 deletions(-)
--
2.20.1
next reply other threads:[~2019-11-06 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:50 Wolfram Sang [this message]
2019-11-06 9:50 ` [RFC PATCH 03/12] macintosh: convert to i2c_new_scanned_device Wolfram Sang
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=20191106095033.25182-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=wsa@the-dreams.de \
/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).