From: Gregor Boirie <gregor.boirie@parrot.com>
To: <linux-iio@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>,
Gregor Boirie <gregor.boirie@parrot.com>
Subject: [PATCH v7 0/1] iio:pressure:ms5611: fix and enhancements
Date: Thu, 17 Mar 2016 12:55:02 +0100 [thread overview]
Message-ID: <cover.1458215358.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
Changes since v4:
* drop first 2 patches since applied
* amend commit to include "Fixes" tag
Changes since v5:
* reword patch subject line and include "Fixes" tag in commit message
Changes since v6:
* use devm_regulator_get to allow dummy regulator usage
* ensure regulator is properly disabled
Regards,
Gregor.
Gregor Boirie (1):
iio:pressure:ms5611: fix missing regulator_disable
drivers/iio/pressure/ms5611.h | 3 +++
drivers/iio/pressure/ms5611_core.c | 41 +++++++++++++++++++++++++++++---------
2 files changed, 35 insertions(+), 9 deletions(-)
--
2.1.4
next reply other threads:[~2016-03-17 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 11:55 Gregor Boirie [this message]
2016-03-17 11:55 ` [PATCH v7 1/1] iio:pressure:ms5611: fix missing regulator_disable Gregor Boirie
2016-03-20 11:03 ` 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.1458215358.git.gregor.boirie@parrot.com \
--to=gregor.boirie@parrot.com \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--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).