From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 0/13] cpumask: cpu_*_map accessors and mm_cpumask()
Date: Fri, 12 Jun 2009 22:59:49 +0930 [thread overview]
Message-ID: <200906122259.49758.rusty@rustcorp.com.au> (raw)
Finally, convert the lagging archs over to using set_cpu_online etc. rather
than frobbing the deprecated cpu_online_map et al. (The new cpu_online_mask
versions are const).
And get ready for variable-length cpumasks in struct mm, by using the
mm_cpumask() accessor.
Cheers,
Rusty.
reply other threads:[~2009-06-12 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200906122259.49758.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@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 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.