From: Jonathan Cameron <jic23@kernel.org>
To: Adinata Tan <adinatatan99@gmail.com>
Cc: lorenzo@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
adinata.softwareengineer@gmail.com
Subject: Re: [PATCH 1/5] iio: humidity: hts221: report available values via read_avail()
Date: Sun, 16 Aug 2026 22:58:01 +0100 [thread overview]
Message-ID: <20260816225801.3fc685be@jic23-huawei> (raw)
In-Reply-To: <CAG442=sn1YnDGdVvfnj6ZaeLknN46EqhAdkYBBp-6AnrrnDGCg@mail.gmail.com>
On Wed, 12 Aug 2026 19:40:05 +0800
Adinata Tan <adinatatan99@gmail.com> wrote:
> Hi Jonathan,
> Thanks for the input. In this case, we can proceed with the current
> implementation?
Busy week so sorry for slow reply.
Yes, that's fine and what I assume you did for v2!
Jonathan
>
> > > For this humidity case in particular, would it be better to keep the legacy
> > > implementation while adding the new read_avail()?
> >
> > To me it seems vanishingly unlikely there is any code out there jumping
> > through the hoops to read the wrong ABI element to figure out a possible
> > value to write to in_humidityrelative_oversampling_ratio
> >
> > So I think this is in the category of ABI that we can change as long
> > as no one notices. For IIO I will also generally take ABI fixes on
> > basis we actually want to know if anyone is using the broken ABI
> > (and they very rarely are!)
next prev parent reply other threads:[~2026-08-16 21:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 9:00 [PATCH 0/5] iio: humidity: hts221: update probe and logging implementations Adi Nata
2026-08-08 9:00 ` [PATCH 1/5] iio: humidity: hts221: report available values via read_avail() Adi Nata
2026-08-10 0:09 ` Jonathan Cameron
2026-08-12 0:22 ` Adinata Tan
2026-08-12 5:04 ` Jonathan Cameron
2026-08-12 11:40 ` Adinata Tan
2026-08-16 21:58 ` Jonathan Cameron [this message]
2026-08-12 0:27 ` Adi
2026-08-08 9:00 ` [PATCH 2/5] iio: humidity: hts221: Add a blank line after variable declarations Adi Nata
2026-08-10 8:40 ` Andy Shevchenko
2026-08-08 9:00 ` [PATCH 3/5] iio: humidity: hts221: Allow unknown whoami for DT fallback Adi Nata
2026-08-10 8:43 ` Andy Shevchenko
2026-08-08 9:00 ` [PATCH 4/5] iio: humidity: hts221: use dev_err_probe() in probe paths Adi Nata
2026-08-10 8:45 ` Andy Shevchenko
2026-08-12 0:31 ` Adi
2026-08-08 9:00 ` [PATCH 5/5] iio: humidity: hts221: fix division by zero in calibration parsing Adi Nata
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=20260816225801.3fc685be@jic23-huawei \
--to=jic23@kernel.org \
--cc=adinata.softwareengineer@gmail.com \
--cc=adinatatan99@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®