devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Nishant Malpani <nish.malpani25@gmail.com>,
	robh+dt@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, mark.rutland@arm.com,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: iio: tsl2563: convert bindings to YAML
Date: Sat, 4 Apr 2020 15:13:41 +0100	[thread overview]
Message-ID: <20200404151341.19388a2e@archlinux> (raw)
In-Reply-To: <20200330225934.GA19255@bogus>

On Mon, 30 Mar 2020 16:59:34 -0600
Rob Herring <robh@kernel.org> wrote:

> On Wed, 18 Mar 2020 12:49:40 +0530, Nishant Malpani wrote:
> > Convert the TSL2563 device tree bindings to the new YAML format.
> > 
> > Signed-off-by: Nishant Malpani <nish.malpani25@gmail.com>
> > ---
> > 
> > Changes in v4:
> >   - Change $id property to reflect corrected relative path.
> > 
> > Changes in v3:
> >   - Include the complete diff (changes from v1).
> > 
> > Changes in v2:
> >   - Rename the dt-bindings to include manufacturer's name.
> >   - Synchronize the bindings with the driver.
> > ---
> >  .../bindings/iio/light/amstaos,tsl2563.yaml   | 49 +++++++++++++++++++
> >  .../devicetree/bindings/iio/light/tsl2563.txt | 19 -------
> >  2 files changed, 49 insertions(+), 19 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/iio/light/amstaos,tsl2563.yaml
> >  delete mode 100644 Documentation/devicetree/bindings/iio/light/tsl2563.txt
> >   
> 
> Reviewed-by: Rob Herring <robh@kernel.org>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.

Thanks,

Jonathan


      reply	other threads:[~2020-04-04 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  7:19 [PATCH v4] dt-bindings: iio: tsl2563: convert bindings to YAML Nishant Malpani
2020-03-30 22:59 ` Rob Herring
2020-04-04 14:13   ` 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=20200404151341.19388a2e@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=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nish.malpani25@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).