From: Carlos Casadiego <cdcp206@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Liviu Stan" <liviu.stan@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"kernel test robot" <lkp@intel.com>,
arnd@arndb.de
Subject: Re: [PATCH v2] iio: temperature: ltc2983: pass leak detector type explicitly
Date: Sat, 3 Oct 2026 16:39:22 -0500 [thread overview]
Message-ID: <asFzGi6etTy1rseZ@archlinux> (raw)
In-Reply-To: <asFViTtGq3hQUrma@ashevche-desk.local>
Thanks for the review.
Noted on ABSOLUTE_ZERO_MILLICELSIUS for a follow-up change.
Cc'ing Arnd as his patch overlaps with this one. I'll wait for the maintainers' preference on the two approaches.
Thanks,
Carlos
En Sat, Oct 03, 2026 at 10:20:41PM +0300, Andy Shevchenko escribió:
> On Fri, Oct 02, 2026 at 11:44:50AM -0500, Carlos Casadiego via B4 Relay wrote:
>
> > __ltc2983_custom_sensor_new() uses propname both to select the firmware
> > property to read and to determine whether the custom sensor is a leak
> > detector.
> >
> > Pass this information explicitly from the caller instead of deriving
> > the sensor type from the firmware property name. This keeps propname
> > limited to identifying the property and preserves the existing
> > conversion behavior.
> >
> > As a side effect, this also avoids the -Wstring-compare warning reported
> > by the kernel test robot for callers where GCC can determine that the
> > property name cannot match "adi,custom-leak-detector".
>
> Reviewed-by: Andy Shevchenko <andy@kernel.org>
>
> ...
>
> > - if ((index % 2) != 0 && !strcmp(propname, "adi,custom-leak-detector"))
> > + if ((index % 2) != 0 && is_leak_detector)
> > temp = temp * 1000000 + 273150000;
>
> A side note for the further changes: We have ABSOLUTE_ZERO_MILLICELSIUS
> that can be used here.
>
> ...
>
> Since Arnd also submitted similar fix, it would be good to Cc him. And in
> general, if there is a clash with the patches addressing same issue, Cc all
> other authors.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
prev parent reply other threads:[~2026-10-03 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 16:44 Carlos Casadiego via B4 Relay
2026-10-03 19:20 ` Andy Shevchenko
2026-10-03 21:39 ` Carlos Casadiego [this message]
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=asFzGi6etTy1rseZ@archlinux \
--to=cdcp206@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=arnd@arndb.de \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.stan@analog.com \
--cc=lkp@intel.com \
--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®