From: Mikko Perttunen <cyndis@kapsi.fi>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
Dmitry Osipenko <digetx@gmail.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/5] ARM: tegra: Add labels to tegra30.dtsi
Date: Wed, 22 Feb 2023 10:56:23 +0200 [thread overview]
Message-ID: <50e64bd0-00cc-fd2f-b45e-e7268cd371b8@kapsi.fi> (raw)
In-Reply-To: <20230221175348.15681-2-clamor95@gmail.com>
On 2/21/23 19:53, Svyatoslav Ryhel wrote:
> From: Michał Mirosław <mirq-linux@rere.qmqm.pl>
>
> Add phandle names for memory/I2C/SPI/USB/SDMMC controller nodes to allow
> for cleaner device descriptions.
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
Hi!
Patches 1 and 2 are missing your Signed-off-by. But also, I'd only add
labels as they are needed instead of adding them all in one go.
Mikko
next prev parent reply other threads:[~2023-02-22 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 17:53 [PATCH v1 0/5] Tegra DTS improvements Svyatoslav Ryhel
2023-02-21 17:53 ` [PATCH v1 1/5] ARM: tegra: Add labels to tegra30.dtsi Svyatoslav Ryhel
2023-02-22 8:56 ` Mikko Perttunen [this message]
2023-02-24 13:34 ` Svyatoslav Ryhel
2023-02-21 17:53 ` [PATCH v1 2/5] ARM: tegra: Add labels to tegra114.dtsi Svyatoslav Ryhel
2023-02-21 17:53 ` [PATCH v1 3/5] ARM: tegra: transformer: use labels for mmc in aliases Svyatoslav Ryhel
2023-02-21 17:53 ` [PATCH v1 4/5] ARM: tegra: asus-tf101: fix accelerometer mount matrix Svyatoslav Ryhel
2023-02-21 17:53 ` [PATCH v1 5/5] tegra30: peripherals: add 266.5MHz nodes Svyatoslav Ryhel
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=50e64bd0-00cc-fd2f-b45e-e7268cd371b8@kapsi.fi \
--to=cyndis@kapsi.fi \
--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 \
--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).