linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] arm: Define cpu_logical_map when CONFIG_SMP is not set
Date: Thu, 5 Jan 2012 15:01:40 +0000	[thread overview]
Message-ID: <20120105150140.GX11810@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1325767486-6392-1-git-send-email-hamo.by@gmail.com>

On Thu, Jan 05, 2012 at 08:44:46PM +0800, hamo.by at gmail.com wrote:
> From: Yang Bai <hamo.by@gmail.com>
> 
> If CONFIG_SMP is not set, define cpu_logical_map(cpu) as
> (cpu), this fixes the problem described in this mail:
> https://lkml.org/lkml/2012/1/2/142

This doesn't solve the reported problem.  asm/smp.h should not be included
by any .c file, and won't be included by linux/smp.h if CONFIG_SMP is not
set.

  reply	other threads:[~2012-01-05 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 12:44 [PATCH RFC] arm: Define cpu_logical_map when CONFIG_SMP is not set hamo.by at gmail.com
2012-01-05 15:01 ` Russell King - ARM Linux [this message]
2012-01-05 16:15   ` Will Deacon

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=20120105150140.GX11810@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 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).