From: Jonathan Cameron <jic23@kernel.org>
To: Tomas Novotny <tomas@novotny.cz>
Cc: linux-iio@vger.kernel.org, "Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Angus Ainslie" <angus@akkea.ca>,
"Marco Felsch" <m.felsch@pengutronix.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Guido Günther" <agx@sigxcpu.org>
Subject: Re: [PATCH v2 0/2] iio: light: vcnl4000: update sampling periods
Date: Fri, 21 Feb 2020 15:12:09 +0000 [thread overview]
Message-ID: <20200221151209.1e9ce807@archlinux> (raw)
In-Reply-To: <20200218154451.13066-1-tomas@novotny.cz>
On Tue, 18 Feb 2020 16:44:49 +0100
Tomas Novotny <tomas@novotny.cz> wrote:
> Vishay has published new information which explain drifts seen in
> experiments. So update the sampling periods for affected variants.
>
> As pointed out in another series, the variable has a misleading name
> (rate instead of period). This will be fixed in the other series to make
> backporting of these patches straightforward.
>
> Tested on vcnl4200. Tests on vcnl4040 done by Guido.
Both applied to the fixes-togreg branch of iio.git and marked as suitable
for stable.
Thanks,
Jonathan
>
> Changes in v2:
> - fix rate -> period in commit messages and subjects
> - collect tags
>
> Tomas Novotny (2):
> iio: light: vcnl4000: update sampling periods for vcnl4200
> iio: light: vcnl4000: update sampling periods for vcnl4040
>
> drivers/iio/light/vcnl4000.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
prev parent reply other threads:[~2020-02-21 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 15:44 [PATCH v2 0/2] iio: light: vcnl4000: update sampling periods Tomas Novotny
2020-02-18 15:44 ` [PATCH v2 1/2] iio: light: vcnl4000: update sampling periods for vcnl4200 Tomas Novotny
2020-02-18 15:44 ` [PATCH v2 2/2] iio: light: vcnl4000: update sampling periods for vcnl4040 Tomas Novotny
2020-02-21 15:12 ` Jonathan Cameron [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=20200221151209.1e9ce807@archlinux \
--to=jic23@kernel.org \
--cc=agx@sigxcpu.org \
--cc=angus@akkea.ca \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=pmeerw@pmeerw.net \
--cc=tglx@linutronix.de \
--cc=tomas@novotny.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.