From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH 0/4] rtc: convert subsystem to i2c_new_dummy_device()
Date: Mon, 22 Jul 2019 19:26:14 +0200 [thread overview]
Message-ID: <20190722172618.4061-1-wsa+renesas@sang-engineering.com> (raw)
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.
The series was generated with coccinelle (audited afterwards, of course) and
build tested by me and by buildbot. No tests on HW have been performed.
The branch is based on v5.3-rc1. A branch (with some more stuff included) can
be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/i2c/new_dummy
Some drivers still need to be manually converted. Patches for those will be
sent out individually.
Wolfram Sang (4):
rtc: isl12026: convert to i2c_new_dummy_device
rtc: max77686: convert to i2c_new_dummy_device
rtc: s35390a: convert to i2c_new_dummy_device
rtc: s5m: convert to i2c_new_dummy_device
drivers/rtc/rtc-isl12026.c | 6 +++---
drivers/rtc/rtc-max77686.c | 6 +++---
drivers/rtc/rtc-s35390a.c | 6 +++---
drivers/rtc/rtc-s5m.c | 6 +++---
4 files changed, 12 insertions(+), 12 deletions(-)
--
2.20.1
next reply other threads:[~2019-07-22 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 17:26 Wolfram Sang [this message]
2019-07-22 17:26 ` [PATCH 1/4] rtc: isl12026: convert to i2c_new_dummy_device Wolfram Sang
2019-07-22 17:26 ` [PATCH 2/4] rtc: max77686: " Wolfram Sang
2019-07-23 15:27 ` Krzysztof Kozlowski
2019-07-22 17:26 ` [PATCH 3/4] rtc: s35390a: " Wolfram Sang
2019-07-22 17:26 ` [PATCH 4/4] rtc: s5m: " Wolfram Sang
2019-07-23 15:32 ` Krzysztof Kozlowski
2019-07-22 20:50 ` [PATCH 0/4] rtc: convert subsystem to i2c_new_dummy_device() Alexandre Belloni
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=20190722172618.4061-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
/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).