From: Stephen Warren <swarren@wwwdotorg.org>
To: Alex Courbot <acourbot@nvidia.com>,
Russell King <linux@arm.linux.org.uk>
Cc: Olof Johansson <olof@lixom.net>, Tomasz Figa <t.figa@samsung.com>,
Dave Martin <Dave.Martin@arm.com>, Arnd Bergmann <arnd@arndb.de>,
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" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v10 0/7] ARM: support for Trusted Foundations secure monitor
Date: Thu, 21 Nov 2013 11:48:54 -0700 [thread overview]
Message-ID: <528E5596.7090606@wwwdotorg.org> (raw)
In-Reply-To: <CAOesGMgcvTFD4u9b7T5HNhuJe_PQyV25Ei++v8hG8AsY_rOdyw@mail.gmail.com>
(Russell, a question for you at the bottom)
On 11/13/2013 10:57 AM, Olof Johansson wrote:
> On Tue, Nov 12, 2013 at 6:14 PM, Alex Courbot <acourbot@nvidia.com> wrote:
>> On 11/13/2013 05:38 AM, Olof Johansson wrote:
...
>>> I pinged Russell, and he brought up the fact that there were earlier
>>> requests to move it to drivers/firmware. It would make sense to try to
>>> get that done before merging, especially if you anticipate someone
>>> using TF on 64-bit platforms.
>>
>> IIRC when we discussed this point your last comment was as follows:
>
> Touche. :) Thanks for the reminder.
>
>> On Tue, Oct 29, 2013 at 6:55 AM, Olof Johansson <olof@lixom.net> wrote:
>>> I think we can probably merge this under arch/arm now, and when we
>>> figure out what needs to be common with ARM64 we can move it out to a
>>> good location. It might be that mostly just a header file with ABI
>>> conventions needs to be shared, not actual implementation, for
>>> example.
>>
>> So I thought we agreed on that. If in the end we prefer to move the ARM
>> firmware interface into drivers/firmware, I'm fine with that too (Tomasz
>> also confirmed he would be ok with it) but I wonder if that would not be
>> somehow premature.
...
> Well, as I already said I'm ok with things going into arch/arm to
> start with, as long as Russell is.
...
Russell, the patch Alex sent to move firmware_ops into drivers/firmware
was rejected, so I don't think we can update this series to move the
code there instead.
So, are you OK with merging this series as-is, in arch/arm/firmware? If
you could ack the patch/series to indicate that, it would be awesome.
Thanks.
next prev parent reply other threads:[~2013-11-21 18:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 10:11 [PATCH v10 0/7] ARM: support for Trusted Foundations secure monitor Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 1/7] ARM: add basic support for Trusted Foundations Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 2/7] of: add vendor prefix for Trusted Logic Mobility Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 3/7] of: add Trusted Foundations bindings Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 4/7] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-11-12 20:23 ` Stephen Warren
2013-11-13 1:59 ` Alex Courbot
2013-11-07 10:11 ` [PATCH v10 5/7] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 6/7] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-11-07 10:11 ` [PATCH v10 7/7] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-11-12 20:26 ` [PATCH v10 0/7] ARM: support for Trusted Foundations secure monitor Stephen Warren
2013-11-12 20:38 ` Olof Johansson
2013-11-13 2:14 ` Alex Courbot
2013-11-13 17:57 ` Olof Johansson
2013-11-14 1:20 ` Alex Courbot
2013-11-17 9:03 ` Alexandre Courbot
2013-11-18 6:28 ` Alex Courbot
2013-11-21 18:48 ` Stephen Warren [this message]
2013-11-21 18:51 ` Olof Johansson
2013-11-21 19:00 ` Russell King - ARM Linux
2013-11-21 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=528E5596.7090606@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Dave.Martin@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--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=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=t.figa@samsung.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