From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans Verkuil <hverkuil+cisco@kernel.org>
Cc: linux-iio@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Subject: Re: [PATCH v2 1/6] media: vidtv: Rename PI definition to PI_SAMPLES
Date: Mon, 16 Mar 2026 13:18:53 +0200 [thread overview]
Message-ID: <abfnHSoZcKJUPAzd@ashevche-desk.local> (raw)
In-Reply-To: <8fcc1419-266c-429e-b1bf-1799322eb69e@kernel.org>
On Mon, Mar 16, 2026 at 11:13:24AM +0100, Hans Verkuil wrote:
>
> Just FYI: I'll take this patch. Regardless of the other patches in this series it does
> make sense.
Thank you!
> I haven't seen any updates to this series, is it abandoned?
There is no consensus which names should be chosen. I have strong opinion about
my choice, some do not agree with. Id est I like the idea to have PI as PI and
not something longer and confusing. Same for 64-bit, just some short.
My rationale is that, in most of the cases the 32-bit value will be used and
having it as is would be nice.
Another point is to have a macro that gives PI rounded to the chosen amount of
digits (to avoid / 10 / 100 / et cetera in the users). I don't know how to
implement that nicely, there is no loops or alike in C preprocessor.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-16 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 20:02 [PATCH v2 0/6] iio: Introduce and use value of π Andy Shevchenko
2025-11-07 20:02 ` [PATCH v2 1/6] media: vidtv: Rename PI definition to PI_SAMPLES Andy Shevchenko
2026-03-16 10:13 ` Hans Verkuil
2026-03-16 11:18 ` Andy Shevchenko [this message]
2025-11-07 20:03 ` [PATCH v2 2/6] units: Add 32- and 64-bit signed values of π Andy Shevchenko
2025-11-07 21:09 ` David Lechner
2025-11-07 21:14 ` David Lechner
[not found] ` <CAHp75VexvdYyjt1GkbfqOotkFpLeb=io6outJ5dpRqBv2qPNng@mail.gmail.com>
2025-11-09 17:00 ` Jonathan Cameron
2025-11-09 17:09 ` Andy Shevchenko
2025-11-07 20:03 ` [PATCH v2 3/6] media: dvb-frontends: atbm8830: Convert to use PI definition Andy Shevchenko
2025-11-07 20:03 ` [PATCH v2 4/6] iio: cros_ec_sensors: " Andy Shevchenko
2025-11-07 20:03 ` [PATCH v2 5/6] iio: frequency: ad9523: " Andy Shevchenko
2025-11-07 20:03 ` [PATCH v2 6/6] iio: position: iqs624-pos: " 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=abfnHSoZcKJUPAzd@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dlechner@baylibre.com \
--cc=dwlsalmeida@gmail.com \
--cc=groeck@chromium.org \
--cc=hverkuil+cisco@kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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®