linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <gnurou@gmail.com>, Dave Martin <Dave.Martin@arm.com>
Cc: Olof Johansson <olof@lixom.net>,
	Mark Rutland <Mark.Rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Kevin Hilman <khilman@linaro.org>,
	Russell King <linux@arm.linux.org.uk>,
	Pawel Moll <pawel.moll@arm.com>, Tomasz Figa <t.figa@samsung.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Alexandre Courbot <acourbot@nvidia.com>,
	"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 v11 7/7] ARM: tegra: support Trusted Foundations by default
Date: Thu, 28 Nov 2013 09:58:33 -0700	[thread overview]
Message-ID: <52977639.4000308@wwwdotorg.org> (raw)
In-Reply-To: <CAAVeFuJgqgRnWLD+dyvb7+2fLanHmdDT0YV5r8ETsoqqjW8p7A@mail.gmail.com>

On 11/27/2013 11:02 PM, Alexandre Courbot wrote:
> On Wed, Nov 27, 2013 at 1:47 AM, Dave Martin <Dave.Martin@arm.com> wrote:
>> On Tue, Nov 26, 2013 at 10:35:58AM +0900, Alexandre Courbot wrote:
>>> On Tue, Nov 26, 2013 at 9:06 AM, Olof Johansson <olof@lixom.net> wrote:
>>>> On Sun, Nov 24, 2013 at 03:30:52PM +0900, Alexandre Courbot wrote:
>>>>> Support for Trusted Foundations is light and allows the kernel to run on
>>>>> a wider range of devices, so enable it by default.
>>>>>
>>>>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
>>>>> Reviewed-by: Tomasz Figa <t.figa@samsung.com>
>>>>> Reviewed-by: Stephen Warren <swarren@nvidia.com>
>>>>> ---
>>>>>  arch/arm/configs/tegra_defconfig | 1 +
>>>>>  1 file changed, 1 insertion(+)
>>>>
>>>> I think we want this enabled on multi_v7_defconfig too? Send a separate
>>>> patch for that once this is merged though.
>>>
>>> Will do.
>>
>> Should it just be default y if one of the relevant
>> CONFIG_ARCH_TEGRA_*_SOC is selected?
>>
>> That way, it's automatically included if relevant, and automatically
>> excluded if not -- regardless of whether the kernel is multiplatform
>> or not.
> 
> So basically, that would mean setting the default to 'y' since the
> option is not available unless a supported platform is included?
> 
> I'm fine this way too, if Stephen also agrees.

Fine by me.


  reply	other threads:[~2013-11-28 16:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24  6:30 [PATCH v11 0/7] ARM: support for the Trusted Foundations secure monitor 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 [this message]
2013-11-28 19:47             ` Dave Martin
2013-11-29  1:07               ` Alex Courbot
2013-11-26  0:10 ` [PATCH v11 0/7] ARM: support for the Trusted Foundations secure monitor Olof Johansson
2013-12-03  0:48   ` 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=52977639.4000308@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --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;
as well as URLs for NNTP newsgroup(s).