From: Jonathan Cameron <jic23@kernel.org>
To: Wadim Mueller <wafgo01@gmail.com>
Cc: "Marcelo Schmitt" <marcelo.schmitt1@gmail.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Maxwell Doose" <m32285159@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] iio: types: add IIO_VOLUMEFLOW channel type
Date: Thu, 4 Jun 2026 09:44:36 +0100 [thread overview]
Message-ID: <20260604094436.3c50f123@jic23-huawei> (raw)
In-Reply-To: <20260602-slf3s-v3-reply-03-wafgo01@gmail.com>
On Wed, 3 Jun 2026 16:08:33 +0200
Wadim Mueller <wafgo01@gmail.com> wrote:
> On Mon, 1 Jun 2026 10:42:33 +0100
> Jonathan Cameron <jic23@kernel.org> wrote:
>
> > I don't think that discussion ever finished. [...]
>
> So i need to decide the unit: l/s or m^3/s? My feeling is l/s. The ranges
> are sub-ml/s, so m^3/s only makes the scale 1e3 smaller and the DECIMAL64
> precision thing worse, for no real benefit in sysfs. If you want strict
> SI i change it. What you prefer?
>
Yes, I'd prefer that for consistency (m^3/sec). Hopefully the scaling is fine
with the new forms that are happy with more leading zeros.
> Wadim
next prev parent reply other threads:[~2026-06-04 8:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 20:54 [PATCH v3 0/3] iio: flow: Sensirion SLF3S liquid flow sensor Wadim Mueller
2026-05-30 20:54 ` [PATCH v3 1/3] iio: types: add IIO_VOLUMEFLOW channel type Wadim Mueller
2026-05-31 18:09 ` Marcelo Schmitt
2026-06-01 9:42 ` Jonathan Cameron
2026-06-03 14:08 ` Wadim Mueller
2026-06-04 8:44 ` Jonathan Cameron [this message]
2026-06-07 10:45 ` Wadim Mueller
2026-06-08 8:53 ` Rodrigo Alencar
2026-06-08 12:24 ` Wadim Mueller
2026-06-09 8:32 ` Rodrigo Alencar
2026-06-03 14:17 ` Andy Shevchenko
2026-05-30 20:54 ` [PATCH v3 2/3] dt-bindings: iio: flow: add Sensirion SLF3S liquid flow sensor Wadim Mueller
2026-05-31 17:45 ` Marcelo Schmitt
2026-05-31 17:50 ` Marcelo Schmitt
2026-06-03 14:08 ` Wadim Mueller
2026-06-03 14:43 ` Marcelo Schmitt
2026-06-03 14:48 ` Krzysztof Kozlowski
2026-06-01 9:44 ` Jonathan Cameron
2026-06-01 11:53 ` Krzysztof Kozlowski
2026-06-01 14:09 ` Jonathan Cameron
2026-06-03 14:08 ` Wadim Mueller
2026-06-03 14:29 ` Krzysztof Kozlowski
2026-06-04 9:03 ` Jonathan Cameron
2026-06-04 11:22 ` Krzysztof Kozlowski
2026-06-05 12:21 ` Jonathan Cameron
2026-06-07 8:30 ` Krzysztof Kozlowski
2026-06-11 10:35 ` Wadim Mueller
2026-06-11 10:42 ` Krzysztof Kozlowski
2026-05-30 20:54 ` [PATCH v3 3/3] iio: flow: add Sensirion SLF3S liquid flow sensor driver Wadim Mueller
2026-05-30 21:14 ` sashiko-bot
2026-05-31 23:59 ` Maxwell Doose
2026-06-01 9:38 ` Jonathan Cameron
2026-06-01 0:45 ` Marcelo Schmitt
2026-06-01 9:41 ` Jonathan Cameron
2026-06-03 14:08 ` Wadim Mueller
2026-06-01 9:53 ` 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=20260604094436.3c50f123@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=marcelo.schmitt1@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=wafgo01@gmail.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