From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH 0/2] RZ/G2x add optee node
Date: Tue, 27 Oct 2020 11:05:36 +0000 [thread overview]
Message-ID: <CA+V-a8t+2ioNTw1m9Xz0_Go=p6dSRWobL15Va5aE3GcWzOHTpA@mail.gmail.com> (raw)
In-Reply-To: <20201023075530.19295-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi Geert,
On Fri, Oct 23, 2020 at 8:55 AM Lad Prabhakar
<prabhakar.mahadev-lad.rj@bp.renesas.com> wrote:
>
> Hi All,
>
> This patch series adds optee node to HiHope RZ/G2{HMN} and EK874 boards.
>
> This patch series applies on top of [1].
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/
> renesas-devel.git/log/?h=renesas-arm-dt-for-v5.11
>
> Cheers,
> Prabhakar
>
> Lad Prabhakar (2):
> arm64: dts: renesas: hihope-common: Add optee node
> arm64: dts: renesas: r8a774c0-ek874: Add optee node
>
As agreed on the irc (optee nodes should be coming from firmware
stack) let's drop these patches.
Cheers,
Prabhakar
> arch/arm64/boot/dts/renesas/hihope-common.dtsi | 7 +++++++
> arch/arm64/boot/dts/renesas/r8a774c0-ek874.dts | 7 +++++++
> 2 files changed, 14 insertions(+)
>
> --
> 2.17.1
>
prev parent reply other threads:[~2020-10-27 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 7:55 [PATCH 0/2] RZ/G2x add optee node Lad Prabhakar
2020-10-23 7:55 ` [PATCH 1/2] arm64: dts: renesas: hihope-common: Add " Lad Prabhakar
2020-10-23 9:49 ` Geert Uytterhoeven
2020-10-23 10:03 ` Lad, Prabhakar
2020-10-23 12:27 ` Geert Uytterhoeven
2020-10-23 7:55 ` [PATCH 2/2] arm64: dts: renesas: r8a774c0-ek874: " Lad Prabhakar
2020-10-27 11:05 ` Lad, Prabhakar [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='CA+V-a8t+2ioNTw1m9Xz0_Go=p6dSRWobL15Va5aE3GcWzOHTpA@mail.gmail.com' \
--to=prabhakar.csengg@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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;
as well as URLs for NNTP newsgroup(s).