devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Mitja Spes <mitja@lxnav.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	"Marc Kleine-Budde" <mkl@pengutronix.de>,
	"Lee Jones" <lee.jones@linaro.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Tomasz Duszynski" <tduszyns@gmail.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] ms5611 sensor value bug fix; dt-binding fix
Date: Sat, 29 Oct 2022 12:40:48 +0100	[thread overview]
Message-ID: <20221029124048.372aed3b@jic23-huawei> (raw)
In-Reply-To: <20221021135827.1444793-1-mitja@lxnav.com>

On Fri, 21 Oct 2022 15:58:19 +0200
Mitja Spes <mitja@lxnav.com> wrote:

> Subject: [PATCH 0/3] ms5611 sensor value bug fix; dt-binding fix
> 
> The first patch fixes a bug in ms5611 iio driver where PROM value
> compensation table was overwritten by the last initialized sensor.
> This in turn produced wrong values when multiple sensors were used.
> 
> Second patch removes the hardcoded SPI frequency and uses the setting
> from dt-bindings.
> 
> Third patch outlines the change from the second patch in the bindings
> example.

1+2 applied to the fixes-togreg branch of iio.git and marked for
stable.

Thanks,

Jonathan

> 
> v2:
> 
> [PATCH 1-2]
> * no change
> 
> [PATCH 3]
> * corrected patch subject
> 
> Mitja Spes (3):
>   iio: pressure: ms5611: fixed value compensation bug
>   iio: pressure: ms5611: changed hardcoded SPI speed to value limited
>   dt-bindings: iio: pressure: meas,ms5611: add max SPI frequency to the
>     example
> 
>  .../bindings/iio/pressure/meas,ms5611.yaml    |  1 +
>  drivers/iio/pressure/ms5611.h                 | 12 ++---
>  drivers/iio/pressure/ms5611_core.c            | 51 ++++++++++---------
>  drivers/iio/pressure/ms5611_spi.c             |  2 +-
>  4 files changed, 33 insertions(+), 33 deletions(-)
> 


      parent reply	other threads:[~2022-10-29 11:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 13:58 [PATCH v2 0/3] ms5611 sensor value bug fix; dt-binding fix Mitja Spes
2022-10-21 13:58 ` [PATCH v2 1/3] iio: pressure: ms5611: fixed value compensation bug Mitja Spes
2022-10-23 11:06   ` Jonathan Cameron
2022-10-24  6:37     ` Mitja Špes
2022-10-21 13:58 ` [PATCH v2 2/3] iio: pressure: ms5611: changed hardcoded SPI speed to value limited Mitja Spes
2022-10-21 15:32   ` Marcus Folkesson
2022-10-23 11:10     ` Jonathan Cameron
2022-10-24  6:46       ` Mitja Špes
2022-10-23 11:12     ` Jonathan Cameron
2022-10-24  9:05       ` Marcus Folkesson
2022-10-21 13:58 ` [PATCH v2 3/3] dt-bindings: iio: pressure: meas,ms5611: add max SPI frequency to the example Mitja Spes
2022-10-21 14:08   ` Krzysztof Kozlowski
2022-10-23 11:14     ` Jonathan Cameron
2022-10-29 11:40 ` 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=20221029124048.372aed3b@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitja@lxnav.com \
    --cc=mkl@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=tduszyns@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).