From: Heiner Kallweit <hkallweit1@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Jean Delvare <jdelvare@suse.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] i2c: Remove I2C_COMPAT config symbol and related code
Date: Mon, 2 Sep 2024 21:54:01 +0200 [thread overview]
Message-ID: <b88626a2-28a5-41a8-9d69-20853858bfea@gmail.com> (raw)
In-Reply-To: <ZtQueK8Y9x0FCWD1@shikoro>
On 01.09.2024 11:06, Wolfram Sang wrote:
> Hi Heiner,
>
> On Wed, Aug 21, 2024 at 10:13:04PM +0200, Heiner Kallweit wrote:
>> This code was added with 2bb5095affdb ("i2c: Provide compatibility links
>> for i2c adapters"). Commit message stated: Provide compatibility links
>> for [...] the time being. We will remove them after a long transition
>> period.
>> 15 years should have been a long enough transition period.
>
> Well, in general, I totally agree.
>
> It seems, however, that this slipped through the cracks. My Debian
> kernelconfig has I2C_COMPAT still enabled, so I am reluctant to remove
> it from one kernel release to the next.
>
> I wonder if we need some printout that it is really going away for a few
> kernel releases.
>
I'm not aware of an option to only warn if the deprecated ABI is accessed
by userspace. So we would have to warn every user if I2C_COMPAT is enabled.
That's something Greg doesn't like. I see his point, but not sure how
to do better.
> Opinions? Jean?
>
> Happy hacking,
>
> Wolfram
>
next prev parent reply other threads:[~2024-09-02 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 20:13 [PATCH] i2c: Remove I2C_COMPAT config symbol and related code Heiner Kallweit
2024-09-01 9:06 ` Wolfram Sang
2024-09-01 20:08 ` Heiner Kallweit
2024-09-02 9:53 ` Wolfram Sang
2024-09-02 19:54 ` Heiner Kallweit [this message]
2024-09-03 10:50 ` Greg KH
2024-09-07 16:32 ` 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=b88626a2-28a5-41a8-9d69-20853858bfea@gmail.com \
--to=hkallweit1@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@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;
as well as URLs for NNTP newsgroup(s).