All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
Cc: linus.walleij@linaro.org, thierry.reding@gmail.com,
	jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
	devicetree@vger.kernel.org, pdeschrijver@nvidia.com,
	josephl@nvidia.com, smangipudi@nvidia.com, ldewangan@nvidia.com,
	vidyas@nvidia.com, Krishna Yarlagadda <kyarlagadda@nvidia.com>
Subject: Re: [PATCH 1/2] dt-binding: Tegra194 pinctrl support
Date: Wed, 1 May 2019 19:46:59 -0500	[thread overview]
Message-ID: <20190502004659.GA8049@bogus> (raw)
In-Reply-To: <1556247378-3335-1-git-send-email-kyarlagadda@nvidia.com>

On Fri, 26 Apr 2019 08:26:17 +0530, Krishna Yarlagadda wrote:
> Add new compatible string and other fields used in pinctrl
> driver for Tegra194 in nvidia,tegra210-pinmux.txt
> 
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> ---
>  .../bindings/pinctrl/nvidia,tegra210-pinmux.txt    | 43 +++++++++++++++++++---
>  1 file changed, 38 insertions(+), 5 deletions(-)
> 

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

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: linus.walleij@linaro.org, thierry.reding@gmail.com,
	jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
	devicetree@vger.kernel.org, pdeschrijver@nvidia.com,
	josephl@nvidia.com, smangipudi@nvidia.com, ldewangan@nvidia.com,
	vidyas@nvidia.com, Krishna Yarlagadda <kyarlagadda@nvidia.com>
Subject: Re: [PATCH 1/2] dt-binding: Tegra194 pinctrl support
Date: Wed, 1 May 2019 19:46:59 -0500	[thread overview]
Message-ID: <20190502004659.GA8049@bogus> (raw)
In-Reply-To: <1556247378-3335-1-git-send-email-kyarlagadda@nvidia.com>

On Fri, 26 Apr 2019 08:26:17 +0530, Krishna Yarlagadda wrote:
> Add new compatible string and other fields used in pinctrl
> driver for Tegra194 in nvidia,tegra210-pinmux.txt
> 
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> ---
>  .../bindings/pinctrl/nvidia,tegra210-pinmux.txt    | 43 +++++++++++++++++++---
>  1 file changed, 38 insertions(+), 5 deletions(-)
> 

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

  parent reply	other threads:[~2019-05-02  0:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  2:56 [PATCH 1/2] dt-binding: Tegra194 pinctrl support Krishna Yarlagadda
2019-04-26  2:56 ` Krishna Yarlagadda
2019-04-26  2:56 ` [PATCH 2/2] pinctrl: tegra: Add Tegra194 pinmux driver Krishna Yarlagadda
2019-04-26  2:56   ` Krishna Yarlagadda
2019-04-26  4:46   ` Vidya Sagar
2019-04-26  4:46     ` Vidya Sagar
2019-04-26  7:11   ` Linus Walleij
2019-04-26  7:11     ` Linus Walleij
2019-04-26 13:16   ` Thierry Reding
2019-04-26 13:05 ` [PATCH 1/2] dt-binding: Tegra194 pinctrl support Thierry Reding
2019-04-26 13:07 ` Thierry Reding
2019-05-02  0:46 ` Rob Herring [this message]
2019-05-02  0:46   ` Rob Herring

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=20190502004659.GA8049@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=josephl@nvidia.com \
    --cc=kyarlagadda@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pdeschrijver@nvidia.com \
    --cc=smangipudi@nvidia.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 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.