From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: linux-mm@kvack.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
aarcange@redhat.com, hannes@cmpxchg.org, mingo@elte.hu,
a.p.zijlstra@chello.nl, torvalds@linux-foundation.org
Subject: Re: [PATCH v2 0/8] THP support for Sparc64
Date: Fri, 5 Oct 2012 15:00:36 -0700 [thread overview]
Message-ID: <20121005150036.edd3be21.akpm@linux-foundation.org> (raw)
In-Reply-To: <20121005.174508.1624534294642226949.davem@davemloft.net>
On Fri, 05 Oct 2012 17:45:08 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Fri, 5 Oct 2012 14:36:44 -0700
>
> > David, I don't know what to do until there's some clarity on the
> > numa/sched changes. Andrea has a new autonuma patchset, Peter's code
> > is in -next and I don't know if it's planned for 3.7 merging. And I
> > suspect (hope) that it won't be merged if that is indeed planned.
>
> It doesn't matter from a sparc64 perspective.
>
> If you remove the autonuma patch, I'll still compile and work.
> I just provide an unused interface.
ah, OK.
> Please do something instead of stalling these changes further.
OK, I'll add it all to the pile and will restage it against mainline on
Monday.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-10-05 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 19:46 [PATCH v2 0/8] THP support for Sparc64 David Miller
2012-10-05 21:36 ` Andrew Morton
2012-10-05 21:45 ` David Miller
2012-10-05 22:00 ` Andrew Morton [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=20121005150036.edd3be21.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=davem@davemloft.net \
--cc=hannes@cmpxchg.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=sparclinux@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).