public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: "Nuno Sá" <noname.nuno@gmail.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: core: Use datasheet name as fallback for label
Date: Tue, 28 Oct 2025 16:51:25 +0200	[thread overview]
Message-ID: <aQDYbRutGLgDmWNu@smile.fi.intel.com> (raw)
In-Reply-To: <CAGb2v676eOkPOc33+FMX6k9562gn34+MR15t-iucLjd0qQKs7Q@mail.gmail.com>

On Tue, Oct 28, 2025 at 10:36:35PM +0800, Chen-Yu Tsai wrote:
> On Tue, Oct 28, 2025 at 5:22 PM Nuno Sá <noname.nuno@gmail.com> wrote:

...

> The axp20x-adc driver currently provides _no_ labels. Would adding labels
> now be considered backward incompatible?

It can be considered forward-incompatible :-)

This kind of discussions happen in IIO in the past and probably still will in
the future. Namely "What should be unique (enough?) string to recognise chip
(platform?)?"

So, you see, we need to answer first "What do we want to recognise?
The platform or the chip?" Then decide what uniquiness will be enough.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-10-28 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 12:42 [PATCH] iio: core: Use datasheet name as fallback for label Chen-Yu Tsai
2025-10-27 14:43 ` Jonathan Cameron
2025-10-28  8:04   ` Andy Shevchenko
2025-10-28  9:22     ` Nuno Sá
2025-10-28 14:36       ` Chen-Yu Tsai
2025-10-28 14:51         ` Andy Shevchenko [this message]
2025-10-28 15:17         ` Nuno Sá
2025-11-02 12:07           ` Jonathan Cameron

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=aQDYbRutGLgDmWNu@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=wens@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