From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Rabin Vincent <rabin@rab.in>
Cc: Jesper Nilsson <jespern@axis.com>,
linux-cris-kernel <linux-cris-kernel@axis.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/6] CRIS: remove SMP code
Date: Fri, 20 Feb 2015 01:33:32 +0100 [thread overview]
Message-ID: <20150220003332.GF11399@axis.com> (raw)
In-Reply-To: <1424374196-4954-2-git-send-email-rabin@rab.in>
On Thu, Feb 19, 2015 at 08:29:52PM +0100, Rabin Vincent wrote:
> The CRIS SMP code cannot be built since there is no (and appears to
> never have been) a CONFIG_SMP Kconfig option in arch/cris/. Remove it.
>
> Signed-off-by: Rabin Vincent <rabin@rab.in>
Nice, added to the queue for the CRIS-tree.
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
next prev parent reply other threads:[~2015-02-20 0:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 19:29 [PATCH 1/6] CRISv32: don't enable irqs in INIT_THREAD Rabin Vincent
2015-02-19 19:29 ` [PATCH 2/6] CRIS: remove SMP code Rabin Vincent
2015-02-20 0:06 ` Paul Bolle
2015-02-20 5:05 ` Mikael Starvik
2015-02-21 0:40 ` Rabin Vincent
2015-02-21 9:14 ` Paul Bolle
2015-02-20 0:33 ` Jesper Nilsson [this message]
2015-02-19 19:29 ` [PATCH 3/6] CRIS: use generic atomic bitops Rabin Vincent
2015-02-20 0:28 ` Jesper Nilsson
2015-02-22 20:07 ` [PATCH] CRISv10: remove redundant macros from system.h Rabin Vincent
2015-02-19 19:29 ` [PATCH 4/6] CRIS: use generic atomic.h Rabin Vincent
2015-02-20 0:32 ` Jesper Nilsson
2015-02-19 19:29 ` [PATCH 5/6] CRIS: use generic cmpxchg.h Rabin Vincent
2015-02-20 0:30 ` Jesper Nilsson
2015-02-19 19:29 ` [PATCH 6/6] CRIS: use generic headers via Kbuild Rabin Vincent
2015-02-20 0:30 ` Jesper Nilsson
2015-02-20 0:27 ` [PATCH 1/6] CRISv32: don't enable irqs in INIT_THREAD Jesper Nilsson
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=20150220003332.GF11399@axis.com \
--to=jesper.nilsson@axis.com \
--cc=jespern@axis.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin@rab.in \
/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