linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Aparna M <a-m1@ti.com>
Cc: bgolaszewski@baylibre.com, linus.walleij@linaro.org,
	a-govindraju@ti.com, robh+dt@kernel.org,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	grygorii.strashko@ti.com, praneeth@ti.com
Subject: Re: [PATCH v5] dt-bindings: gpio: Convert TI TPIC2810 GPIO Controller bindings to YAML
Date: Thu, 24 Feb 2022 11:35:53 -0600	[thread overview]
Message-ID: <YhfB+c6zMiCjbE96@robh.at.kernel.org> (raw)
In-Reply-To: <20220223174215.17838-1-a-m1@ti.com>

On Wed, 23 Feb 2022 23:12:15 +0530, Aparna M wrote:
> Convert gpio-tpic2810 bindings to yaml format and remove outdated
> bindings in .txt format.
> 
> Signed-off-by: Aparna M <a-m1@ti.com>
> ---
> 
> v4 -> v5: Fix indentation issues
> v3 -> v4: Add gpio-line-names property
> v2 -> v3: Remove redundant descriptions and make minor change in example
> v1 -> v2: Fix identation issues and update commit message
> 
>  .../bindings/gpio/gpio-tpic2810.txt           | 16 ------
>  .../bindings/gpio/gpio-tpic2810.yaml          | 51 +++++++++++++++++++
>  2 files changed, 51 insertions(+), 16 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/gpio/gpio-tpic2810.txt
>  create mode 100644 Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-02-24 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 17:42 [PATCH v5] dt-bindings: gpio: Convert TI TPIC2810 GPIO Controller bindings to YAML Aparna M
2022-02-24 17:35 ` Rob Herring [this message]
2022-03-15  1:01 ` Linus Walleij
2022-05-05  8:58   ` M, Aparna
2022-07-07  5:19     ` Vignesh Raghavendra
2022-07-07 11:19       ` Linus Walleij
2022-07-08  5:24         ` Vignesh Raghavendra
2022-07-08 15:50           ` Bartosz Golaszewski

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=YhfB+c6zMiCjbE96@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=a-govindraju@ti.com \
    --cc=a-m1@ti.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=praneeth@ti.com \
    --cc=robh+dt@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).