linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregor Boirie <gregor.boirie@parrot.com>
To: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	Tomasz Duszynski <tduszyns@gmail.com>,
	Daniel Baluta <daniel.baluta@intel.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Mark Brown <broonie@kernel.org>, "Andrew F. Davis" <afd@ti.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Gregor Boirie <gregor.boirie@parrot.com>
Subject: [PATCH v4 0/3] iio:pressure:ms5611: fix and enhancements
Date: Tue, 1 Mar 2016 11:31:35 +0100	[thread overview]
Message-ID: <cover.1456828051.git.gregor.boirie@parrot.com> (raw)

Changes since v1:
* temperature compensation fix:
    * reword commit message
    * remove useless parenthesis
* power regulator: reword commit message
* add oversampling rate support

Changes since v2:
* remove non printable characters from commit messages

Changes since v3:
* drop first 3 patches since applied onto testing
* fix oops at regulator probing time if regulator support not compiled-in
* complete device-tree support and documentation
* remove continuous sampling support (see Jonathan's "kthread tight loop
  trigger" proposal)
* checkpatch'ed

Gregor Boirie (2):
  iio:pressure:ms5611: fix oops when probing regulator
  iio:pressure:ms5611: oversampling rate support

Grégor Boirie (1):
  iio:pressure:ms5611: complete DT support

 .../devicetree/bindings/iio/pressure/ms5611.txt    |  19 ++++
 .../devicetree/bindings/vendor-prefixes.txt        |   1 +
 drivers/iio/pressure/ms5611.h                      |  20 ++--
 drivers/iio/pressure/ms5611_core.c                 | 113 ++++++++++++++++++++-
 drivers/iio/pressure/ms5611_i2c.c                  |  25 +++--
 drivers/iio/pressure/ms5611_spi.c                  |  32 ++++--
 6 files changed, 185 insertions(+), 25 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/iio/pressure/ms5611.txt

-- 
2.1.4


             reply	other threads:[~2016-03-01 10:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 10:31 Gregor Boirie [this message]
2016-03-01 10:31 ` [PATCH v4 1/3] iio:pressure:ms5611: fix oops when probing regulator Gregor Boirie
2016-03-05 14:36   ` Jonathan Cameron
2016-03-01 10:31 ` [PATCH v4 2/3] iio:pressure:ms5611: complete DT support Gregor Boirie
2016-03-05  4:25   ` Rob Herring
2016-03-05 14:40   ` Jonathan Cameron
2016-03-01 10:31 ` [PATCH v4 3/3] iio:pressure:ms5611: oversampling rate support Gregor Boirie
2016-03-05 14:45   ` 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=cover.1456828051.git.gregor.boirie@parrot.com \
    --to=gregor.boirie@parrot.com \
    --cc=afd@ti.com \
    --cc=broonie@kernel.org \
    --cc=daniel.baluta@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jic23@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=tduszyns@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;
as well as URLs for NNTP newsgroup(s).