linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: 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 11:53:47 +0200	[thread overview]
Message-ID: <ZtWLK5WVczDLlvdo@shikoro> (raw)
In-Reply-To: <b41c44d9-75f9-4c45-ad95-e896179a6249@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]


> > 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.
> > 
> One reason may be that the default for I2C_COMPAT is still y.
> We should switch this to n, even though it doesn't help in cases like
> make oldconfig.

Yes, but we should still do it.

> > I wonder if we need some printout that it is really going away for a few
> > kernel releases.
> > 
> This may be a compromise.
> However I wonder how likely it is that somebody uses the latest kernel
> and hasn't updated his userspace tools for > 15 yrs.

I am not worrying about using old versions of lmsensors, this is super
unlikely. I worry about custom applications using the deprecated path.
Like, IPMI docs advertised this path up to now (I fixed it). And why
should one change that path if the kernel is not complaining?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-09-02  9:53 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 [this message]
2024-09-02 19:54   ` Heiner Kallweit
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=ZtWLK5WVczDLlvdo@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=hkallweit1@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@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).