From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Li Yang <leoyang.li@nxp.com>
Subject: Re: [PATCH] arm64: dts: ls1028a: add optee node
Date: Mon, 30 Nov 2020 17:29:18 +0800 [thread overview]
Message-ID: <20201130092917.GC4072@dragon> (raw)
In-Reply-To: <20201115225314.8114-1-michael@walle.cc>
On Sun, Nov 15, 2020 at 11:53:14PM +0100, Michael Walle wrote:
> Add the optee node which can either be enabled by a specific board or by
> the bootloader.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: ls1028a: add optee node
Date: Mon, 30 Nov 2020 17:29:18 +0800 [thread overview]
Message-ID: <20201130092917.GC4072@dragon> (raw)
In-Reply-To: <20201115225314.8114-1-michael@walle.cc>
On Sun, Nov 15, 2020 at 11:53:14PM +0100, Michael Walle wrote:
> Add the optee node which can either be enabled by a specific board or by
> the bootloader.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
Applied, thanks.
next prev parent reply other threads:[~2020-11-30 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 22:53 [PATCH] arm64: dts: ls1028a: add optee node Michael Walle
2020-11-15 22:53 ` Michael Walle
2020-11-30 9:29 ` Shawn Guo [this message]
2020-11-30 9:29 ` Shawn Guo
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=20201130092917.GC4072@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.