From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Maxime Ripard <mripard@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: ad7192: Fix Regulator Properties
Date: Sun, 6 Oct 2019 10:59:39 +0100 [thread overview]
Message-ID: <20191006105939.5e3fb2b1@archlinux> (raw)
In-Reply-To: <20191002191416.GA17605@bogus>
On Wed, 2 Oct 2019 14:14:16 -0500
Rob Herring <robh@kernel.org> wrote:
> On Wed, 2 Oct 2019 16:45:41 +0200, Maxime Ripard wrote:
> > The AD7192 binding describes two regulator properties, avdd-supply and
> > dvdd-supply, but describes it as a constant string that must be avdd and
> > dvdd. This is wrong since a *-supply property is actually a phandle, and
> > results in warnings when the example is validated (or any device tree using
> > that device, for that matter).
> >
> > Let's remove that requirement.
> >
> > Fixes: f7356e47032c ("dt-bindings: iio: adc: ad7192: Add binding documentation for AD7192")
> > Signed-off-by: Maxime Ripard <mripard@kernel.org>
> > ---
> > Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml | 4 ----
> > 1 file changed, 4 deletions(-)
> >
>
> Applied, thanks.
>
> Rob
Thanks for clearing this up.
Jonathan
prev parent reply other threads:[~2019-10-06 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 14:45 [PATCH 1/2] dt-bindings: iio: ad7192: Fix Regulator Properties Maxime Ripard
2019-10-02 14:45 ` [PATCH 2/2] dt-bindings: iio: ad7192: Fix DTC warning in the example Maxime Ripard
2019-10-02 19:14 ` Rob Herring
2019-10-02 19:14 ` [PATCH 1/2] dt-bindings: iio: ad7192: Fix Regulator Properties Rob Herring
2019-10-06 9:59 ` Jonathan Cameron [this message]
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=20191006105939.5e3fb2b1@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.