From: Arjan van de Ven <arjan@linux.intel.com>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, Neil Brown <neilb@suse.de>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2 of 4] cpumask: export cpu_online_map and cpu_possible_map consistently
Date: Fri, 04 Aug 2006 07:45:45 -0700 [thread overview]
Message-ID: <44D35D99.601@linux.intel.com> (raw)
In-Reply-To: <1154669759.21040.2353.camel@hole.melbourne.sgi.com>
Greg Banks wrote:
> cpumask: ensure that the cpu_online_map and cpu_possible_map bitmasks,
> and hence all the macros in <linux/cpumask.h> that require them, are
> available to modules for all supported combinations of architecture
> and CONFIG_SMP.
Are there any actual users of this?
next prev parent reply other threads:[~2006-08-04 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 5:35 PATCH 2 of 4] cpumask: export cpu_online_map and cpu_possible_map consistently Greg Banks
2006-08-04 14:32 ` Zwane Mwaikambo
2006-08-07 3:05 ` Greg Banks
2006-08-04 14:45 ` Arjan van de Ven [this message]
2006-08-07 2:57 ` Greg Banks
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=44D35D99.601@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=gnb@melbourne.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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