From: Heiner Kallweit <hkallweit1@gmail.com>
To: Wolfram Sang <wsa@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] i2c: core: Switch I2C_COMPAT to default n
Date: Mon, 2 Sep 2024 21:01:18 +0200 [thread overview]
Message-ID: <8e618f52-413c-41c1-9ac2-0260a1904792@gmail.com> (raw)
In-Reply-To: <4660a46b-9128-4407-8baa-f257245784a3@gmail.com>
I2C_COMPAT has been considered deprecated for 15 years now.
Therefore make it default n, before we remove support for it
in the near future.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
drivers/i2c/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig
index 44710267d..e5721cebb 100644
--- a/drivers/i2c/Kconfig
+++ b/drivers/i2c/Kconfig
@@ -42,11 +42,11 @@ config I2C_BOARDINFO
config I2C_COMPAT
bool "Enable compatibility bits for old user-space"
- default y
+ default n
help
Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
other user-space package which expects i2c adapters to be class
- devices. If you don't know, say Y.
+ devices. If you don't know, say N.
config I2C_CHARDEV
tristate "I2C device interface"
--
2.46.0
next prev parent reply other threads:[~2024-09-02 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 19:00 [PATCH 0/2] i2c: core: prepare dropping support for I2C_COMPAT Heiner Kallweit
2024-09-02 19:01 ` Heiner Kallweit [this message]
2024-09-03 8:49 ` [PATCH 1/2] i2c: core: Switch I2C_COMPAT to default n Greg Kroah-Hartman
2024-09-02 19:02 ` [PATCH 2/2] driver core: class: warn if a compatibility class is registered Heiner Kallweit
2024-09-02 19:20 ` Greg Kroah-Hartman
2024-09-03 9:04 ` Wolfram Sang
2024-09-03 9:06 ` Wolfram Sang
2024-09-03 10:06 ` Greg Kroah-Hartman
2024-09-03 10:43 ` Wolfram Sang
2024-09-03 10:50 ` Greg Kroah-Hartman
2024-09-03 11:09 ` 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=8e618f52-413c-41c1-9ac2-0260a1904792@gmail.com \
--to=hkallweit1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=wsa@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).