linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: kyarlagadda@nvidia.com, kthota@nvidia.com,
	lorenzo.pieralisi@arm.com, linux-kernel@vger.kernel.org,
	mmaddireddy@nvidia.com, linux-tegra@vger.kernel.org,
	robh+dt@kernel.org, sagar.tv@gmail.com,
	amurray@thegoodpenguin.co.uk, thierry.reding@gmail.com,
	jonathanh@nvidia.com, jckuo@nvidia.com,
	devicetree@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Fix entry name for I/O High Voltage property
Date: Fri, 30 Oct 2020 13:32:56 -0500	[thread overview]
Message-ID: <20201030183256.GA4112134@bogus> (raw)
In-Reply-To: <20201026063902.14744-1-vidyas@nvidia.com>

On Mon, 26 Oct 2020 12:09:01 +0530, Vidya Sagar wrote:
> Correct the name of the I/O High Voltage Property from
> 'nvidia,io-high-voltage' to 'nvidia,io-hv'.
> 
> Fixes: 2585a584f844 ("pinctrl: Add Tegra194 pinctrl DT bindings")
> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> ---
>  .../devicetree/bindings/pinctrl/nvidia,tegra194-pinmux.txt      | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

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

  parent reply	other threads:[~2020-10-30 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26  6:39 [PATCH 1/2] dt-bindings: Fix entry name for I/O High Voltage property Vidya Sagar
2020-10-26  6:39 ` [PATCH 2/2] arm64: tegra: Fix DT binding for IO High Voltage entry Vidya Sagar
2020-10-30 18:32 ` Rob Herring [this message]
2020-11-10 17:44 ` [PATCH 1/2] dt-bindings: Fix entry name for I/O High Voltage property Thierry Reding

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=20201030183256.GA4112134@bogus \
    --to=robh@kernel.org \
    --cc=amurray@thegoodpenguin.co.uk \
    --cc=devicetree@vger.kernel.org \
    --cc=jckuo@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=kthota@nvidia.com \
    --cc=kyarlagadda@nvidia.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mmaddireddy@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=vidyas@nvidia.com \
    /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).