From: Rusty Russell <rusty@rustcorp.com.au>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Jack Steiner <steiner@sgi.com>
Subject: Re: [PATCH 1/4] cpumask: cpu_coregroup_mask(): x86
Date: Thu, 18 Dec 2008 16:44:00 +1030 [thread overview]
Message-ID: <200812181644.00796.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4949831B.2000809@sgi.com>
On Thursday 18 December 2008 09:24:19 Mike Travis wrote:
> Rusty Russell wrote:
> > Like cpu_coregroup_map, but returns a (const) pointer.
> >
> > (This will go to Ingo separately as part of the x86 series, just
> > airing it here for thoroughness).
> >
> > Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> > Signed-off-by: Mike Travis <travis@sgi.com>
> > Cc: Ingo Molnar <mingo@redhat.com>
>
> I've pulled this patch into the queue for my cpus4096-for-ingo tree.
>
> [PATCH 1/4] cpumask: cpu_coregroup_mask(): x86
>
> I can also line up a queue for sched related changes:
>
> [PATCH 4/4] cpumask: Replace cpu_coregroup_map with cpu_coregroup_map()
>
> Is there any status on the corresponding changes for sparc, s390? (I assume
> that they'll need to be merged into linux-next?)
>
> [PATCH 2/4] cpumask: cpu_coregroup_mask(): sparc
> [PATCH 3/4] cpumask: cpu_coregroup_mask(): s390
You can't take 4/4 until 2/4 and 3/4 are merged, and since it's not
x86-specific as well, we'll leave it in my tree.
Thanks,
Rusty.
prev parent reply other threads:[~2008-12-18 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812011646.35018.rusty@rustcorp.com.au>
2008-12-17 22:54 ` [PATCH 1/4] cpumask: cpu_coregroup_mask(): x86 Mike Travis
2008-12-17 23:02 ` Mike Travis
2008-12-18 6:14 ` Rusty Russell [this message]
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=200812181644.00796.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=steiner@sgi.com \
--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).