linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5][3/15] smp_call_function/_on_cpu - i386
Date: 09 Feb 2003 09:18:05 -0600	[thread overview]
Message-ID: <1044803887.1979.39.camel@mulgrave> (raw)



The voyager pieces of this don't provide the smp_call_function_on_cpu(),
since voyager doesn't compile kernel/smp.c, so voyager will break the
first time someone uses the new function.

As a general comment, wouldn't it be better simply to make
smp_call_function an alias for smp_call_function_on_cpu with the mask
being the cpu_online_map?  That way we'd reduce the amount of duplicated
code.

James



             reply	other threads:[~2003-02-09 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-09 15:18 James Bottomley [this message]
2003-02-09 16:24 ` [PATCH][2.5][3/15] smp_call_function/_on_cpu - i386 Zwane Mwaikambo
  -- strict thread matches above, loose matches on Subject: below --
2003-02-09 12:05 Zwane Mwaikambo

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=1044803887.1979.39.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@holomorphy.com \
    /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).