From: Anton Blanchard <anton@samba.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/3] powerpc: Add form 1 NUMA affinity
Date: Fri, 30 Apr 2010 17:33:12 +1000 [thread overview]
Message-ID: <20100430073312.GA14636@kryten> (raw)
In-Reply-To: <1272612299.13814.0.camel@pasglop>
Hi Ben,
> I sent your previous version of that one to Linus, it's already up. Can
> you check it's allright ?
No change to this patch, but I thought I would send them as a series since they
build on each other. I'll double check mainline looks good.
Anton
prev parent reply other threads:[~2010-04-30 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 4:33 [PATCH 1/3] powerpc: Set a smaller value for RECLAIM_DISTANCE to enable zone reclaim Anton Blanchard
2010-04-30 4:34 ` [PATCH 2/3] powerpc: Add form 1 NUMA affinity Anton Blanchard
2010-04-30 4:43 ` [PATCH 3/3] powerpc: Use form 1 affinity to setup node distance Anton Blanchard
2010-05-06 6:50 ` Benjamin Herrenschmidt
2010-04-30 7:24 ` [PATCH 2/3] powerpc: Add form 1 NUMA affinity Benjamin Herrenschmidt
2010-04-30 7:33 ` Anton Blanchard [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=20100430073312.GA14636@kryten \
--to=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).