From: Matt Ranostay <matt.ranostay@konsulko.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v6 0/3] iio: chemical: atlas-sensor: add DO support
Date: Mon, 27 Apr 2020 21:30:30 -0700 [thread overview]
Message-ID: <CAJCx=gnEySbyLQA9u=nVJ3-Wk+++Ch6L9C-bYP_EFSz-7TKkhg@mail.gmail.com> (raw)
In-Reply-To: <20200413181031.68e101da@archlinux>
On Mon, Apr 13, 2020 at 10:10 AM Jonathan Cameron <jic23@kernel.org> wrote:
>
>
>
> Hi Matt,
>
> Found this still in my queue and to be honest I'm lost and
> can't easily figure out what the status is (I'm too lazy to
> read all the past threads).
>
> So what do you think the status of this patch set is?
The code is merged but just noticed the documentation patch somehow got dropped.
Thanks,
Matt
>
> Thanks,
>
> Jonathan
>
> On Sun, 9 Feb 2020 16:10:55 -0800
> Matt Ranostay <matt.ranostay@konsulko.com> wrote:
>
> > Changes from v1:
> > * combined dt binding docs
> > * added making interrupt line is optional patchset
> > * broke out dt changes from DO-SM module patchset
> >
> > Changes from v2:
> > * switch docs to YAML format
> >
> > Changes from v3:
> > * fix up issues reported with dt-schema
> >
> > Changes from v4:
> > * fix logic issue in optional interrupt patchset
> >
> > Changes from v5:
> > * Update license on yaml conversion to GPLv2.0+ and BSD clause
> >
> > Matt Ranostay (3):
> > iio: chemical: atlas-sensor: allow probe without interrupt line
> > iio: chemical: atlas-sensor: add DO-SM module support
> > dt-bindings: iio: chemical: consolidate atlas-sensor docs
> >
> > .../bindings/iio/chemical/atlas,ec-sm.txt | 21 -----
> > .../bindings/iio/chemical/atlas,orp-sm.txt | 21 -----
> > .../bindings/iio/chemical/atlas,ph-sm.txt | 21 -----
> > .../bindings/iio/chemical/atlas,sensor.yaml | 53 +++++++++++
> > drivers/iio/chemical/atlas-sensor.c | 91 +++++++++++++++----
> > 5 files changed, 125 insertions(+), 82 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,ec-sm.txt
> > delete mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,orp-sm.txt
> > delete mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,ph-sm.txt
> > create mode 100644 Documentation/devicetree/bindings/iio/chemical/atlas,sensor.yaml
> >
>
next prev parent reply other threads:[~2020-04-28 4:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 0:10 [PATCH v6 0/3] iio: chemical: atlas-sensor: add DO support Matt Ranostay
2020-02-10 0:10 ` [PATCH v6 1/3] iio: chemical: atlas-sensor: allow probe without interrupt line Matt Ranostay
2020-02-14 14:24 ` Jonathan Cameron
2020-02-15 22:43 ` Matt Ranostay
2020-02-10 0:10 ` [PATCH v6 2/3] iio: chemical: atlas-sensor: add DO-SM module support Matt Ranostay
2020-02-10 0:10 ` [PATCH v6 3/3] dt-bindings: iio: chemical: consolidate atlas-sensor docs Matt Ranostay
2020-04-13 17:10 ` [PATCH v6 0/3] iio: chemical: atlas-sensor: add DO support Jonathan Cameron
2020-04-28 4:30 ` Matt Ranostay [this message]
2020-05-02 16:23 ` Jonathan Cameron
2020-05-03 23:50 ` Matt Ranostay
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='CAJCx=gnEySbyLQA9u=nVJ3-Wk+++Ch6L9C-bYP_EFSz-7TKkhg@mail.gmail.com' \
--to=matt.ranostay@konsulko.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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).