From: Alison Schofield <amsfield22@gmail.com>
To: Matt Ranostay <mranostay@gmail.com>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org
Subject: Re: [PATCH 0/2] iio: humidity: sht31: add Sensirion SHT31 support
Date: Mon, 13 Jun 2016 15:25:04 -0700 [thread overview]
Message-ID: <20160613222502.GA4376@d830.WORKGROUP> (raw)
In-Reply-To: <1465708397-19649-1-git-send-email-mranostay@gmail.com>
On Sat, Jun 11, 2016 at 10:13:15PM -0700, Matt Ranostay wrote:
> Add support for the humidity and temperature functionally for the SHT31
> chipset. In addition add support for using using software triggers.
Now that I'm hwmon-aware ;) I see this same driver under review in hwmon.
Can support exist in 2 places?
alisons
>
> Matt Ranostay (2):
> devicetree: add Sensirion AG vendor id
> iio: humidity: sht31: add Sensirion SHT31 support
>
> .../devicetree/bindings/i2c/trivial-devices.txt | 1 +
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> drivers/iio/humidity/Kconfig | 11 +
> drivers/iio/humidity/Makefile | 1 +
> drivers/iio/humidity/sht31.c | 416 +++++++++++++++++++++
> 5 files changed, 430 insertions(+)
> create mode 100644 drivers/iio/humidity/sht31.c
>
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-13 22:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 5:13 [PATCH 0/2] iio: humidity: sht31: add Sensirion SHT31 support Matt Ranostay
2016-06-12 5:13 ` [PATCH 1/2] devicetree: add Sensirion AG vendor id Matt Ranostay
2016-06-14 22:06 ` Rob Herring
2016-06-12 5:13 ` [PATCH 2/2] iio: humidity: sht31: add Sensirion SHT31 support Matt Ranostay
2016-06-12 5:35 ` Matt Ranostay
2016-06-13 22:25 ` Alison Schofield [this message]
2016-06-13 23:23 ` [PATCH 0/2] " Matt Ranostay
2016-06-14 7:44 ` jic23
2016-06-14 19:01 ` Matt Ranostay
2016-06-15 4:18 ` Guenter Roeck
2016-06-15 16:31 ` Jonathan Cameron
2016-06-15 18:48 ` Guenter Roeck
2016-06-15 19:34 ` 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=20160613222502.GA4376@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mranostay@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