From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: Re: next: voyager: sm/smp.h:205: error: 'smp_ops' undeclared
Date: Wed, 10 Jun 2009 19:14:11 +0000 [thread overview]
Message-ID: <1244661251.17432.22.camel@mulgrave.site> (raw)
In-Reply-To: <a4423d670906100448o161fb18am1868878c827376b5@mail.gmail.com>
On Wed, 2009-06-10 at 15:48 +0400, Alexander Beregalov wrote:
> Hi
>
> arch/x86/include/asm/smp.h: In function 'hard_smp_processor_id':
> arch/x86/include/asm/smp.h:205: error: 'smp_ops' undeclared (first use
> in this function)
>
> The code
> static inline int hard_smp_processor_id(void)
> {
> return smp_ops.hard_smp_processor_id();
> }
> should be under #ifdef CONFIG_SMP
Actually, that won't work either ... it turns out the UP IO-APIC case
needs hard_smp_processor_id(). I'm starting to think that turning it
into an smp_ops function was the wrong thing to do.
James
prev parent reply other threads:[~2009-06-10 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 11:48 next: voyager: sm/smp.h:205: error: 'smp_ops' undeclared Alexander Beregalov
2009-06-10 19:14 ` James Bottomley [this message]
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=1244661251.17432.22.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=a.beregalov@gmail.com \
--cc=linux-next@vger.kernel.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