All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: trusted_foundations: fix compile error on non-SMP
Date: Fri, 23 May 2014 21:28:51 +0200	[thread overview]
Message-ID: <201405232128.51247.arnd@arndb.de> (raw)
In-Reply-To: <537F7E1F.4020706@wwwdotorg.org>

On Friday 23 May 2014, Stephen Warren wrote:
> On 05/22/2014 06:23 PM, Alexandre Courbot wrote:
> > The setup_max_cpus variable is only defined if CONFIG_SMP is set. Add
> > a preprocessor condition to avoid the following compilation error if
> > CONFIG_SMP is not set:
> > 
> >     arch/arm/include/asm/trusted_foundations.h: In function 'register_trusted_foundations':
> >     arch/arm/include/asm/trusted_foundations.h:57:2: error: 'setup_max_cpus' undeclared (first use in this function)
> > 
> > Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> > Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> 
> I spoke to Olof and IRC, and he said arm-soc would be OK taking this
> patch, since they applied the original code this fixes. IIUC, they'll
> pick this up directly.
> 
> Acked-by: Stephen Warren <swarren@nvidia.com>
> 

Pulled into the fixes branch now, thanks!

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <acourbot@nvidia.com>,
	Olof Johansson <olof@lixom.net>,
	"arm@kernel.org" <arm@kernel.org>,
	Stephen Warren <swarren@nvidia.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] ARM: trusted_foundations: fix compile error on non-SMP
Date: Fri, 23 May 2014 21:28:51 +0200	[thread overview]
Message-ID: <201405232128.51247.arnd@arndb.de> (raw)
In-Reply-To: <537F7E1F.4020706@wwwdotorg.org>

On Friday 23 May 2014, Stephen Warren wrote:
> On 05/22/2014 06:23 PM, Alexandre Courbot wrote:
> > The setup_max_cpus variable is only defined if CONFIG_SMP is set. Add
> > a preprocessor condition to avoid the following compilation error if
> > CONFIG_SMP is not set:
> > 
> >     arch/arm/include/asm/trusted_foundations.h: In function 'register_trusted_foundations':
> >     arch/arm/include/asm/trusted_foundations.h:57:2: error: 'setup_max_cpus' undeclared (first use in this function)
> > 
> > Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> > Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> 
> I spoke to Olof and IRC, and he said arm-soc would be OK taking this
> patch, since they applied the original code this fixes. IIUC, they'll
> pick this up directly.
> 
> Acked-by: Stephen Warren <swarren@nvidia.com>
> 

Pulled into the fixes branch now, thanks!

	Arnd

  reply	other threads:[~2014-05-23 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  0:23 [PATCH RESEND] ARM: trusted_foundations: fix compile error on non-SMP Alexandre Courbot
2014-05-23  0:23 ` Alexandre Courbot
2014-05-23 16:58 ` Stephen Warren
2014-05-23 16:58   ` Stephen Warren
2014-05-23 19:28   ` Arnd Bergmann [this message]
2014-05-23 19:28     ` Arnd Bergmann
2014-05-23 18:24 ` Sergei Shtylyov
2014-05-23 18:24   ` Sergei Shtylyov
2014-05-23 19:27   ` Arnd Bergmann
2014-05-23 19:27     ` Arnd Bergmann

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=201405232128.51247.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.