From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Bence Csókás" <csokas.bence@prolan.hu>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Cc: Samuel Holland <samuel@sholland.org>, Sebastian Reichel <sre@kernel.org>
Subject: [PATCH v2 0/2] i2c: Reduce use of i2c_of_match_device()
Date: Thu, 13 Feb 2025 13:45:03 +0200 [thread overview]
Message-ID: <20250213114613.2646933-1-andriy.shevchenko@linux.intel.com> (raw)
The i2c_of_match_device() was developed as internal API and was exported just
in case well before we get an idea of the generic helper for getting driver
data for the matched device. For all the times of i2c_of_match_device() being
exported there were _only_ three users, two of which had been already converted
to better API. For preventing the use of i2c_of_match_device(), make it private
to I²C subsystem.
This is assumed to go via I²C tree, but can be done differently taking into
account the immutable tag or branch for involved subsystems.
In v2:
- collected tags (Sebastian)
- removed one leftover in the first patch
Andy Shevchenko (2):
power: ip5xxx_power: Make use of i2c_get_match_data()
i2c: Unexport i2c_of_match_device()
drivers/i2c/i2c-core-of.c | 1 -
drivers/i2c/i2c-core.h | 9 +++++++++
drivers/power/supply/ip5xxx_power.c | 7 ++-----
include/linux/i2c.h | 11 -----------
4 files changed, 11 insertions(+), 17 deletions(-)
--
2.45.1.3035.g276e886db78b
next reply other threads:[~2025-02-13 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 11:45 Andy Shevchenko [this message]
2025-02-13 11:45 ` [PATCH v2 1/2] power: ip5xxx_power: Make use of i2c_get_match_data() Andy Shevchenko
2025-02-13 12:09 ` Vladimir Zapolskiy
2025-02-13 12:24 ` Vladimir Zapolskiy
2025-02-13 15:51 ` Wolfram Sang
2025-02-13 11:45 ` [PATCH v2 2/2] i2c: Unexport i2c_of_match_device() Andy Shevchenko
2025-02-13 12:08 ` Vladimir Zapolskiy
2025-02-13 15:51 ` 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=20250213114613.2646933-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=csokas.bence@prolan.hu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=samuel@sholland.org \
--cc=sebastian.reichel@collabora.com \
--cc=sre@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