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:27:56 +0200 [thread overview]
Message-ID: <201405232127.56481.arnd@arndb.de> (raw)
In-Reply-To: <537F9267.7090304@cogentembedded.com>
On Friday 23 May 2014, Sergei Shtylyov wrote:
> > +#if IS_ENABLED(CONFIG_SMP)
>
> if (IS_ENABLED(CONFIG_SMP))
>
> > setup_max_cpus = 0;
> > +#endif
>
That wouldn't help to fix the build error when setup_max_cpus is not declared.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
Olof Johansson <olof@lixom.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] ARM: trusted_foundations: fix compile error on non-SMP
Date: Fri, 23 May 2014 21:27:56 +0200 [thread overview]
Message-ID: <201405232127.56481.arnd@arndb.de> (raw)
In-Reply-To: <537F9267.7090304@cogentembedded.com>
On Friday 23 May 2014, Sergei Shtylyov wrote:
> > +#if IS_ENABLED(CONFIG_SMP)
>
> if (IS_ENABLED(CONFIG_SMP))
>
> > setup_max_cpus = 0;
> > +#endif
>
That wouldn't help to fix the build error when setup_max_cpus is not declared.
Arnd
next prev parent reply other threads:[~2014-05-23 19:27 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
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 [this message]
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=201405232127.56481.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.