From: Doug Anderson <dianders@chromium.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Daniel Campello <campello@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-iio <linux-iio@vger.kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/3] dt-bindings: iio: Add bindings for sx9310 sensor
Date: Fri, 24 Jul 2020 13:39:25 -0700 [thread overview]
Message-ID: <CAD=FV=VRDWH8wgX5EC3S_dw_riDoY=X4EVY8BbD3ctmA6Wi+GA@mail.gmail.com> (raw)
In-Reply-To: <20200723230344.1422750-2-swboyd@chromium.org>
Hi,
On Thu, Jul 23, 2020 at 4:03 PM Stephen Boyd <swboyd@chromium.org> wrote:
>
> From: Daniel Campello <campello@chromium.org>
>
> Adds device tree bandings for sx9310 sensor.
>
> Signed-off-by: Daniel Campello <campello@chromium.org>
> Cc: Hartmut Knaack <knaack.h@gmx.de>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
> Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> [swboyd@chromium.org: Add both regulators and make them optional]
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> .../iio/proximity/semtech,sx9310.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
Reviewed-by: Douglas Anderson <dianders@chromium.org>
next prev parent reply other threads:[~2020-07-24 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 23:03 [PATCH 0/3] Some sx9310 iio driver updates Stephen Boyd
2020-07-23 23:03 ` [PATCH 1/3] dt-bindings: iio: Add bindings for sx9310 sensor Stephen Boyd
2020-07-24 20:39 ` Doug Anderson [this message]
2020-07-23 23:03 ` [PATCH 2/3] iio: sx9310: Add newlines to printks Stephen Boyd
2020-07-24 20:27 ` Doug Anderson
2020-07-24 20:43 ` Daniel Campello
2020-07-23 23:03 ` [PATCH 3/3] iio: sx9310: Enable regulator for svdd supply Stephen Boyd
2020-07-24 20:25 ` Doug Anderson
2020-07-24 20:36 ` Stephen Boyd
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='CAD=FV=VRDWH8wgX5EC3S_dw_riDoY=X4EVY8BbD3ctmA6Wi+GA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=campello@chromium.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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).