From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: cpumask changes
Date: Thu, 11 Jun 2009 22:53:40 +0930 [thread overview]
Message-ID: <200906112253.41039.rusty@rustcorp.com.au> (raw)
Hi Stephen,
As discussed, the cpumask changes are in a different tree. linux-next tends
to find all kinds of compile arch issues with these.
http://ozlabs.org/~rusty/kernel/rr-latest-cpumask.tar.bz2
Thanks,
Rusty.
next reply other threads:[~2009-06-11 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 13:23 Rusty Russell [this message]
2009-06-11 14:41 ` cpumask changes Stephen Rothwell
2009-06-14 1:10 ` Stephen Rothwell
2009-06-14 5:20 ` Rusty Russell
2009-06-14 6:07 ` Stephen Rothwell
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=200906112253.41039.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.