From: "Leonidas P." <papadakospan@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: jose.abreu@synopsys.com, Mark Rutland <mark.rutland@arm.com>,
Carlos de Paula <me@carlosedp.com>,
Jonas Karlman <jonas@kwiboo.se>,
Katsuhiro Suzuki <katsuhiro@katsuster.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Peter Geis <pgwipeout@gmail.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Johan Jonker <jbx6244@gmail.com>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
Christoph Muellner <christoph.muellner@theobroma-systems.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Add txpbl node for RK3399/RK3328
Date: Sun, 01 Mar 2020 04:06:54 +0200 [thread overview]
Message-ID: <1583028414.33600.0@gmail.com> (raw)
In-Reply-To: <6132615.msM8OCcsVu@phil>
I am also in favor of this but I think we should remove the line that
specifies the txpbl in the rk3328-roc-cc.dts gmac2io since it will get
applied here in the .dtsi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-01 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 22:10 [PATCH] arm64: dts: rockchip: Add txpbl node for RK3399/RK3328 Carlos de Paula
2020-03-01 0:25 ` Heiko Stuebner
2020-03-01 2:06 ` Leonidas P. [this message]
2020-03-01 8:22 ` Daniel Lezcano
2020-03-01 9:02 ` Daniel Lezcano
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=1583028414.33600.0@gmail.com \
--to=papadakospan@gmail.com \
--cc=christoph.muellner@theobroma-systems.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=jonas@kwiboo.se \
--cc=jose.abreu@synopsys.com \
--cc=katsuhiro@katsuster.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=me@carlosedp.com \
--cc=pgwipeout@gmail.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.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).