From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Tegra DTS improvements
Date: Tue, 4 Apr 2023 15:33:12 +0200 [thread overview]
Message-ID: <168061516877.2141244.5510663138589135443.b4-ty@nvidia.com> (raw)
In-Reply-To: <20230329090403.5274-1-clamor95@gmail.com>
From: Thierry Reding <treding@nvidia.com>
On Wed, 29 Mar 2023 12:03:59 +0300, Svyatoslav Ryhel wrote:
> Path for mmc devices are replaced with labels for
> better tree comprehension. CPU paths are replaced with
> labels references as well. Fixed accelerometer mount
> matrix for TF101. Added 266.5MHz peripheral opp node
> for devices which need it.
>
Applied, thanks!
[1/4] ARM: tegra: transformer: use labels for mmc in aliases
(no commit info)
[2/4] ARM: tegra30: Use cpu* labels
(no commit info)
[3/4] ARM: tegra: asus-tf101: fix accelerometer mount matrix
(no commit info)
[4/4] ARM: tegra30: peripherals: add 266.5MHz nodes
(no commit info)
Best regards,
--
Thierry Reding <treding@nvidia.com>
prev parent reply other threads:[~2023-04-04 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 9:03 Svyatoslav Ryhel
2023-03-29 9:04 ` [PATCH v3 1/4] ARM: tegra: transformer: use labels for mmc in aliases Svyatoslav Ryhel
2023-06-16 15:24 ` Svyatoslav Ryhel
2023-03-29 9:04 ` [PATCH v3 2/4] ARM: tegra30: Use cpu* labels Svyatoslav Ryhel
2023-04-04 13:33 ` (subset) " Thierry Reding
2023-03-29 9:04 ` [PATCH v3 3/4] ARM: tegra: asus-tf101: fix accelerometer mount matrix Svyatoslav Ryhel
2023-04-04 13:33 ` (subset) " Thierry Reding
2023-03-29 9:04 ` [PATCH v3 4/4] ARM: tegra30: peripherals: add 266.5MHz nodes Svyatoslav Ryhel
2023-04-04 13:33 ` (subset) " Thierry Reding
2023-04-04 13:33 ` Thierry Reding [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=168061516877.2141244.5510663138589135443.b4-ty@nvidia.com \
--to=thierry.reding@gmail.com \
--cc=clamor95@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maxim.schwalm@gmail.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
all inboxes | Powered by JetHome®