From: Rob Herring <robh@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: jason@lakedaemon.net, thierry.reding@gmail.com,
jonathanh@nvidia.com, dmaengine@vger.kernel.org,
vkoul@kernel.org, robh+dt@kernel.org, devicetree@vger.kernel.org,
tglx@linutronix.de, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, maz@kernel.org
Subject: Re: [PATCH 3/4] dt-bindings: interrupt-controller: arm,gic: Update Tegra compatibles
Date: Thu, 5 Nov 2020 12:58:50 -0600 [thread overview]
Message-ID: <20201105185850.GA1633758@bogus> (raw)
In-Reply-To: <1604571846-14037-4-git-send-email-spujar@nvidia.com>
On Thu, 05 Nov 2020 15:54:05 +0530, Sameer Pujar wrote:
> Update Tegra compatibles to support newer Tegra chips and required
> combinations.
>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
> .../devicetree/bindings/interrupt-controller/arm,gic.yaml | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
With the indentation fixed:
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-11-05 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:24 [PATCH 0/4] Convert few Tegra docs to json-schema Sameer Pujar
2020-11-05 10:24 ` [PATCH 1/4] arm64: tegra: Rename ADMA device nodes for Tegra210 Sameer Pujar
2020-11-05 10:24 ` [PATCH 2/4] dt-bindings: dma: Convert ADMA doc to json-schema Sameer Pujar
2020-11-05 18:50 ` Rob Herring
2020-11-05 18:56 ` Rob Herring
2020-11-05 10:24 ` [PATCH 3/4] dt-bindings: interrupt-controller: arm,gic: Update Tegra compatibles Sameer Pujar
2020-11-05 18:57 ` Rob Herring
2020-11-05 18:58 ` Rob Herring [this message]
2020-11-05 10:24 ` [PATCH 4/4] dt-bindings: bus: Convert ACONNECT doc to json-schema Sameer Pujar
2020-11-05 19:05 ` Rob Herring
2020-11-06 6:44 ` Sameer Pujar
2020-11-06 14:37 ` 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=20201105185850.GA1633758@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=spujar@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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 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.