From: Rusty Russell <rusty@rustcorp.com.au>
To: Mike Travis <travis@sgi.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Greg KH <gregkh@suse.de>
Subject: Re: linux-next: rr series import failure
Date: Thu, 18 Dec 2008 11:19:16 +1030 [thread overview]
Message-ID: <200812181119.16550.rusty@rustcorp.com.au> (raw)
In-Reply-To: <494998ED.6080206@sgi.com>
On Thursday 18 December 2008 10:57:25 Mike Travis wrote:
> > cpumask:add_sysfs_displays_for_configured_and_disabled_cpu_maps.patch
> Rusty - do you want to do this in your rr queue?
Once Greg's happy and Ack'ed, and we've run it through normal tests, I'll
put it in the cpumask git tree and Ingo can simply merge it from there.
Thanks,
Rusty.
next prev parent reply other threads:[~2008-12-18 0:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 23:50 linux-next: rr series import failure Stephen Rothwell
2008-12-18 0:27 ` Mike Travis
2008-12-18 0:49 ` Rusty Russell [this message]
2008-12-18 10:36 ` Ingo Molnar
2008-12-18 0:44 ` Rusty Russell
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=200812181119.16550.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=gregkh@suse.de \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=travis@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).