From: Olof Johansson <olof@lixom.net>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Tomasz Figa <t.figa@samsung.com>,
Dave Martin <Dave.Martin@arm.com>,
Kevin Hilman <khilman@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <Mark.Rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, gnurou@gmail.com
Subject: Re: [PATCH v11 0/7] ARM: support for the Trusted Foundations secure monitor
Date: Mon, 25 Nov 2013 16:10:33 -0800 [thread overview]
Message-ID: <20131126001033.GB21634@quad.lixom.net> (raw)
In-Reply-To: <1385274652-16415-1-git-send-email-acourbot@nvidia.com>
On Sun, Nov 24, 2013 at 03:30:45PM +0900, Alexandre Courbot wrote:
> New rebase that should be ready-to-apply on the latest Tegra tree. The last
> remaining blocker is Russell's approval for this series and it is my hope to
> obtain it with this version.
>
> There has been quite some debate around this series, notably about the SMC
> calling conventions and whether the firmware interface should be moved out of
> arch/arm. I hope that all the questions have been answered and that we can move
> forward with this series that enables NVIDIA-branded retail Tegra devices to run
> mainline.
>
> Changes since v10:
> - Rebased on top of more recent sources since some files have been renamed in
> mach-tegra.
> - Gave a final proof-read and extensive testing.
>
> Alexandre Courbot (7):
> ARM: add basic support for Trusted Foundations
> of: add vendor prefix for Trusted Logic Mobility
> of: add Trusted Foundations bindings documentation
> ARM: tegra: add support for Trusted Foundations
> ARM: tegra: split setting of CPU reset handler
> ARM: tegra: set CPU reset handler using firmware
> ARM: tegra: support Trusted Foundations by default
Ok, this looks good to me. Russell, do you want the first patch in your
tree or are you ok with acking that and we can take everything through
arm-soc?
The alternative is that we can have Stephen provide a stable branch with
the first patch on it and we both merge that, then the rest goes on top
of that through arm-soc.
Thanks!
-Olof
next prev parent reply other threads:[~2013-11-26 0:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 6:30 Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 1/7] ARM: add basic support for Trusted Foundations Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 2/7] of: add vendor prefix for Trusted Logic Mobility Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 3/7] of: add Trusted Foundations bindings documentation Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 4/7] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 5/7] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 6/7] ARM: tegra: set CPU reset handler using firmware Alexandre Courbot
2013-11-24 6:30 ` [PATCH v11 7/7] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-11-26 0:06 ` Olof Johansson
2013-11-26 1:35 ` Alexandre Courbot
2013-11-26 16:47 ` Dave Martin
2013-11-28 6:02 ` Alexandre Courbot
2013-11-28 16:58 ` Stephen Warren
2013-11-28 19:47 ` Dave Martin
2013-11-29 1:07 ` Alex Courbot
2013-11-26 0:10 ` Olof Johansson [this message]
2013-12-03 0:48 ` [PATCH v11 0/7] ARM: support for the Trusted Foundations secure monitor Alexandre Courbot
2013-12-09 17:21 ` Stephen Warren
2013-12-13 19:57 ` Stephen Warren
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=20131126001033.GB21634@quad.lixom.net \
--to=olof@lixom.net \
--cc=Dave.Martin@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=acourbot@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=t.figa@samsung.com \
--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
all inboxes | Powered by JetHome®