From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpumask: introduce new API, without changing anything
Date: Mon, 10 Nov 2008 10:16:47 -0800 [thread overview]
Message-ID: <49187A8F.5010502@sgi.com> (raw)
In-Reply-To: <20081108122833.GH8354@elte.hu>
Ingo Molnar wrote:
...
> Mike, could you please double-check that the version that is in
> tip/cpus4096 [622e0ed] is the final version you need, and that if you
> base subsequent patches on it it works as expected?
...
I'm checking this out, so far it looks good.
> and once that patch hits upstream, we could restructure/rebase the
> commits in cpus4096-v2 ontop of upstream and spread them out properly.
> Does that sound optimal?
Yes, thanks. I'm doing the x86 portion now. Rusty is doing the other
arch and core changes.
next prev parent reply other threads:[~2008-11-10 18:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081029152849.3883d072.sfr@canb.auug.org.au>
[not found] ` <200811021229.16061.rusty@rustcorp.com.au>
[not found] ` <alpine.LFD.2.00.0811011834360.3483@nehalem.linux-foundation.org>
2008-11-06 22:49 ` [PATCH] cpumask: introduce new API, without changing anything Rusty Russell
2008-11-07 8:40 ` Ingo Molnar
2008-11-07 8:52 ` Andrew Morton
2008-11-07 8:57 ` Ingo Molnar
2008-11-07 11:32 ` Rusty Russell
2008-11-07 9:11 ` Stephen Rothwell
2008-11-07 9:39 ` Ingo Molnar
2008-11-07 12:24 ` Ingo Molnar
2008-11-07 18:17 ` Mike Travis
2008-11-08 9:24 ` Rusty Russell
2008-11-08 12:28 ` Ingo Molnar
2008-11-10 18:16 ` Mike Travis [this message]
2008-11-09 20:01 ` Linus Torvalds
2008-11-09 20:16 ` Ingo Molnar
2008-11-09 21:37 ` Ingo Molnar
2008-11-09 21:46 ` 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=49187A8F.5010502@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox