All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Manfred Spraul" <manfred@colorfullife.com>
To: "Russ Weight" <rweight@us.ibm.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Scalable CPU bitmasks
Date: Mon, 18 Mar 2002 23:28:47 +0100	[thread overview]
Message-ID: <001e01c1cecc$50c347f0$010411ac@local> (raw)

>
>
>  NOTE:   The cpumap_to_ulong() and cpumap_ulong_to_cpumap() interfaces
>          are provided specifically for migration. In their current
>          form, they call BUG() if NR_CPUS is defined to be greater
>          than the bit-size of (unsigned long).

Why BUG? NR_CPUS is known at compile time,  is there a reason why you
can't use a call to an undefined function in order to get a link time
error message? (like __bad_udelay in linux/asm-i386/udelay.h)

--
    Manfred





             reply	other threads:[~2002-03-18 22:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 22:28 Manfred Spraul [this message]
2002-03-18 22:42 ` [PATCH] Scalable CPU bitmasks Tim Hockin
2002-03-18 22:44   ` Russ Weight
  -- strict thread matches above, loose matches on Subject: below --
2002-03-18 22:07 Russ Weight
2002-03-19 11:28 ` Denis Vlasenko
2002-03-19  7:56   ` Andrew Morton
2002-03-20 23:04   ` Russ Weight
2002-01-30  0:32 Russ Weight

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='001e01c1cecc$50c347f0$010411ac@local' \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rweight@us.ibm.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 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.