From: Jan Remes <ciakval@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Joe Sandom" <joe.g.sandom@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jan Remes" <jan.remes@mycroftmind.com>,
stable@vger.kernel.org,
"Martin Triska" <martin.triska@mycroftmind.com>
Subject: Re: [PATCH 1/4] iio: light: tsl2591: don't divide by zero
Date: Wed, 14 Oct 2026 10:29:03 +0200 [thread overview]
Message-ID: <as89TxIwfpw7x40g@mm-ntb-00805> (raw)
In-Reply-To: <as5zy1LRyE5hr6vn@ashevche-desk.local>
On Tue, 13 Oct 2026 21:09:15 +0300, Andy Shevchenko wrote:
> On Tue, Oct 13, 2026 at 04:39:40PM +0200, Jan Remes wrote:
> >
> > Fixes: 2335f0d7c790 ("iio: light: Added AMS tsl2591 driver implementation")
> > Cc: stable@vger.kernel.org
> > Reported-by: Martin Triska <martin.triska@mycroftmind.com>
>
> How was it reported? Offline? Off the list?
> Otherwise we have Closes tag to point to the report
Yes, this was reported off-the-list in an internal report at $DAYJOB.
--
Kind regards,
Jan Remes
next prev parent reply other threads:[~2026-10-14 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 14:39 [PATCH 0/4] iio: light: tsl2591: fix lux calculation and precision, add I2C ID table, report saturation Jan Remes
2026-10-13 14:39 ` [PATCH 1/4] iio: light: tsl2591: don't divide by zero Jan Remes
2026-10-13 18:09 ` Andy Shevchenko
2026-10-14 8:29 ` Jan Remes [this message]
2026-10-13 14:39 ` [PATCH 2/4] iio: light: tsl2591: add I2C device ID table Jan Remes
2026-10-13 18:24 ` Andy Shevchenko
2026-10-13 14:39 ` [PATCH 3/4] iio: light: tsl2591: report saturation Jan Remes
2026-10-13 14:39 ` [PATCH 4/4] iio: light: tsl2591: improve lux calculation precision Jan Remes
2026-10-13 18:27 ` 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=as89TxIwfpw7x40g@mm-ntb-00805 \
--to=ciakval@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jan.remes@mycroftmind.com \
--cc=jic23@kernel.org \
--cc=joe.g.sandom@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.triska@mycroftmind.com \
--cc=nuno.sa@analog.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®