From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
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,
gerald.schaefer@de.ibm.com
Subject: Re: [PATCH 0/8] THP support for Sparc64
Date: Wed, 03 Oct 2012 22:00:27 -0400 (EDT) [thread overview]
Message-ID: <20121003.220027.1636081487098835868.davem@davemloft.net> (raw)
In-Reply-To: <20121002155544.2c67b1e8.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Tue, 2 Oct 2012 15:55:44 -0700
> I had a shot at integrating all this onto the pending stuff in linux-next.
> "mm: Add and use update_mmu_cache_pmd() in transparent huge page code."
> needed minor massaging in huge_memory.c. But as Andrea mentioned, we
> ran aground on Gerald's
> http://ozlabs.org/~akpm/mmotm/broken-out/thp-remove-assumptions-on-pgtable_t-type.patch,
> part of the thp-for-s390 work.
While working on a rebase relative to this work, I noticed that the
s390 patches don't even compile.
It's because of that pmd_pgprot() change from Peter Z. which arrives
asynchonously via the linux-next tree. It makes THP start using
pmd_pgprot() (a new interface) which the s390 patches don't provide.
It's going to require that I do new work for my sparc64 THP changes as
well.
--
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>
next prev parent reply other threads:[~2012-10-04 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 22:26 [PATCH 0/8] THP support for Sparc64 David Miller
2012-10-02 22:55 ` Andrew Morton
2012-10-03 0:53 ` David Miller
2012-10-04 2:00 ` David Miller [this message]
2012-10-04 10:35 ` Andrea Arcangeli
2012-10-04 18:11 ` David Miller
2012-10-05 9:28 ` Michal Hocko
2012-10-05 11:57 ` Andrea Arcangeli
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=20121003.220027.1636081487098835868.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sparclinux@vger.kernel.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).