From: "David S. Miller" <davem@davemloft.net>
To: viro@ftp.linux.org.uk
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] highest_possible_processor_id() has to be a macro
Date: Sun, 16 Oct 2005 00:16:49 -0700 (PDT) [thread overview]
Message-ID: <20051016.001649.94729039.davem@davemloft.net> (raw)
In-Reply-To: <20051015235112.GA7992@ftp.linux.org.uk>
From: Al Viro <viro@ftp.linux.org.uk>
Date: Sun, 16 Oct 2005 00:51:12 +0100
> ... otherwise, things like alpha and sparc64 break and break
> badly. They define cpu_possible_map to something else in smp.h
> *AFTER* having included cpumask.h.
So ugly...
But, it's the best fix for now.
Longer term we might want to make an asm/cpumask.h that can
help allow the platforms to cleanly say "well, mask X is
equivalent to Y, so only instantiate X and define Y to X"
which is all that these two platforms are trying to accomplish.
If you don't support cpu hotplug, present == possible afterall.
next prev parent reply other threads:[~2005-10-16 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 23:51 Al Viro
2005-10-16 7:16 ` David S. Miller [this message]
2005-10-16 7:43 ` Herbert Xu
2005-10-16 7:46 ` Al Viro
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=20051016.001649.94729039.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®