public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Svyatoslav Ryhel" <clamor95@gmail.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 3/3] misc: Remove old APDS990x driver
Date: Mon, 20 Apr 2026 11:21:02 +0300	[thread overview]
Message-ID: <aeXh7j410AxESy4U@ashevche-desk.local> (raw)
In-Reply-To: <20260419172216.3cf10e51@jic23-huawei>

On Sun, Apr 19, 2026 at 05:22:16PM +0100, Jonathan Cameron wrote:
> On Sun, 19 Apr 2026 16:41:24 +0300
> Svyatoslav Ryhel <clamor95@gmail.com> wrote:
> > нд, 19 квіт. 2026 р. о 16:33 Jonathan Cameron <jic23@kernel.org> пише:
> > > On Sun, 19 Apr 2026 11:31:24 +0300
> > > Svyatoslav Ryhel <clamor95@gmail.com> wrote:

...

> > > There is the obvious point of ABI compatibility raised as well, but given
> > > we don't seem to be getting much push back on that maybe that's not a significant
> > > concern.  
> > 
> > I did not found any ABI in the Documentation/ABI regarding this sensor
> > using grep,

The code is what is in use, it has an ABI. The question if it's in use or not.

> > maybe you are more familiar?

> Doesn't matter if it's documented explicitly (many older drivers are not).
> The question is whether anyone has supported parts and userspace code that
> makes use of the sysfs files this driver provides.
> 
> Their userspace will be broken by dropping it.  The lack of upstream users
> makes this less critical but it can be argued it's still a possible regression.

Usual recommendation is to google, and check Debian code search engine.
I randomly chose a couple of sysfs nodes and only kernel code refers to them.
So, at least there is a good sign that it likely not in use. But one has
to perform more checks (all attributes, more sources of information) and
summarise that in the commit message.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-04-20  8:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-19  8:31 [PATCH v2 0/3] Update APDS990x ALS to support device trees Svyatoslav Ryhel
2026-04-19  8:31 ` [PATCH v2 1/3] dt-bindings: iio: light: Document Avago APDS9900/9901 ALS/Proximity sensor Svyatoslav Ryhel
2026-04-19  8:31 ` [PATCH v2 2/3] iio: tsl2772: add support for " Svyatoslav Ryhel
2026-04-19 11:29   ` Jonathan Cameron
2026-04-19 11:50     ` Svyatoslav Ryhel
2026-04-19 16:24       ` Jonathan Cameron
2026-04-19 13:37   ` Jonathan Cameron
2026-04-19 13:46     ` Svyatoslav Ryhel
2026-04-19 16:24       ` Jonathan Cameron
2026-04-19 16:28         ` Svyatoslav Ryhel
2026-04-19  8:31 ` [PATCH v2 3/3] misc: Remove old APDS990x driver Svyatoslav Ryhel
2026-04-19  8:42   ` Greg Kroah-Hartman
2026-04-19 13:33   ` Jonathan Cameron
2026-04-19 13:41     ` Svyatoslav Ryhel
2026-04-19 16:22       ` Jonathan Cameron
2026-04-20  8:21         ` Andy Shevchenko [this message]
2026-04-20  8:33           ` Arnd Bergmann
2026-04-20  8:41             ` Andy Shevchenko

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=aeXh7j410AxESy4U@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=arnd@arndb.de \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=rdunlap@infradead.org \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.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