From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devicetree@vger.kernel.org, Jon Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: memory: Document Tegra210 EMC table
Date: Tue, 4 Jan 2022 13:13:56 -0600 [thread overview]
Message-ID: <YdScdFvwLfAlp9Gf@robh.at.kernel.org> (raw)
In-Reply-To: <20211217165919.2700920-1-thierry.reding@gmail.com>
On Fri, 17 Dec 2021 17:59:15 +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Add device tree bindings for the Tegra210 EMC table that is passed via a
> reserved-memory device tree node.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../nvidia,tegra210-emc-table.yaml | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reserved-memory/nvidia,tegra210-emc-table.yaml
>
This one appears to stand on its own, so applied, thanks!
prev parent reply other threads:[~2022-01-04 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 16:59 [PATCH 1/5] dt-bindings: memory: Document Tegra210 EMC table Thierry Reding
2021-12-17 16:59 ` [PATCH 2/5] dt-bindings: memory: Add Tegra210 memory controller bindings Thierry Reding
2021-12-18 10:59 ` Krzysztof Kozlowski
2021-12-17 16:59 ` [PATCH 3/5] dt-bindings: memory: Add Tegra114 " Thierry Reding
2021-12-18 11:02 ` Krzysztof Kozlowski
2021-12-18 18:08 ` Rob Herring
2021-12-17 16:59 ` [PATCH 4/5] dt-bindings: memory: tegra: Fix Tegra132 compatible string Thierry Reding
2021-12-18 18:08 ` Rob Herring
2022-01-04 19:13 ` Rob Herring
2021-12-17 16:59 ` [PATCH 5/5] dt-bindings: memory: tegra210: Mark EMC as cooling device Thierry Reding
2021-12-22 17:20 ` Rob Herring
2022-01-04 19:13 ` Rob Herring [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=YdScdFvwLfAlp9Gf@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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).