From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Phil Reid <preid@electromag.com.au>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
mark.rutland@arm.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, michal.simek@xilinx.com
Subject: Re: [PATCH v2 1/2] dt-binding: iio: Add optional label property
Date: Sat, 5 Oct 2019 15:58:11 +0100 [thread overview]
Message-ID: <20191005155811.29374f19@archlinux> (raw)
In-Reply-To: <20190927144419.GA26041@bogus>
On Fri, 27 Sep 2019 09:44:19 -0500
Rob Herring <robh@kernel.org> wrote:
> On Thu, Sep 19, 2019 at 10:36:07PM +0800, Phil Reid wrote:
> > This optional property defines a symbolic name for the device.
> > This helps to distinguish between more than one iio device
> > of the same type.
> >
> > Suggested-by: Michal Simek <michal.simek@xilinx.com>
> > Signed-off-by: Phil Reid <preid@electromag.com.au>
> > ---
> > Documentation/devicetree/bindings/iio/iio-bindings.txt | 5 +++++
> > 1 file changed, 5 insertions(+)
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Applied to the togreg branch of iio.git and pushed out as testing
for nothing much to happen to it.
Thanks,
Jonathan
next prev parent reply other threads:[~2019-10-05 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 14:36 [PATCH v2 0/2] iio: core: Add optional symbolic label to device attributes Phil Reid
2019-09-19 14:36 ` [PATCH v2 1/2] dt-binding: iio: Add optional label property Phil Reid
2019-09-27 14:44 ` Rob Herring
2019-10-05 14:58 ` Jonathan Cameron [this message]
2019-09-19 14:36 ` [PATCH v2 2/2] iio: core: Add optional symbolic label to device attributes Phil Reid
2019-10-05 14:59 ` Jonathan Cameron
2019-10-07 20:32 ` Jonathan Cameron
2019-10-08 7:06 ` Phil Reid
2019-10-08 12:40 ` 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=20191005155811.29374f19@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pmeerw@pmeerw.net \
--cc=preid@electromag.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox