From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tomasz Figa <tomasz.figa@gmail.com>,
Dave Martin <Dave.Martin@arm.com>,
gnurou@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations
Date: Tue, 03 Sep 2013 12:42:23 -0600 [thread overview]
Message-ID: <52262D8F.9060706@wwwdotorg.org> (raw)
In-Reply-To: <1377770268-14014-1-git-send-email-acourbot@nvidia.com>
On 08/29/2013 03:57 AM, Alexandre Courbot wrote:
> New version revised according to comments received for v3. Hopefully
> it will be good enough to be merged.
Aside from the small issue in patch 1/5, the series,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-09-03 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 9:57 [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 1/5] ARM: add basic Trusted Foundations support Alexandre Courbot
2013-08-30 8:20 ` Tomasz Figa
2013-09-02 7:28 ` Alexandre Courbot
2013-09-03 18:36 ` Stephen Warren
2013-09-03 18:40 ` Stephen Warren
2013-08-29 9:57 ` [PATCH v4 2/5] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 3/5] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 4/5] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 5/5] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-08-30 8:23 ` [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations Tomasz Figa
2013-09-03 18:42 ` Stephen Warren [this message]
2013-09-04 2:31 ` Alex Courbot
2013-09-04 18:25 ` 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=52262D8F.9060706@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Dave.Martin@arm.com \
--cc=acourbot@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--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=tomasz.figa@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