From: acourbot@nvidia.com (Alex Courbot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations
Date: Wed, 4 Sep 2013 11:31:46 +0900 [thread overview]
Message-ID: <52269B92.3070304@nvidia.com> (raw)
In-Reply-To: <52262D8F.9060706@wwwdotorg.org>
On 09/04/2013 03:42 AM, Stephen Warren wrote:
> 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>
Thanks! I have adressed the issues you mentioned and will submit v5
soon. Despite the fact this adds some non-Tegra stuff, will you be able
to take it into your tree, or should I ask someone else?
next prev parent reply other threads:[~2013-09-04 2:31 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
2013-09-04 2:31 ` Alex Courbot [this message]
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=52269B92.3070304@nvidia.com \
--to=acourbot@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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