From: Yisheng Xie <xieyisheng1@huawei.com>
To: Will Deacon <will.deacon@arm.com>
Cc: akpm@linux-foundation.org, mhocko@kernel.org,
guohanjun@huawei.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mhocko@suse.com,
dave.hansen@intel.com, sudeep.holla@arm.com,
catalin.marinas@arm.com, mark.rutland@arm.com,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
mike.kravetz@oracle.com, n-horiguchi@ah.jp.nec.com
Subject: Re: [RFC PATCH v3 0/2] arm64/hugetlb: enable gigantic page
Date: Sat, 27 Aug 2016 17:45:45 +0800 [thread overview]
Message-ID: <ec6fd8e5-37df-d212-0247-6f9454eafb8e@huawei.com> (raw)
In-Reply-To: <20160826102617.GG13554@arm.com>
Hi Andrew,
Can this patchset be merged? Or have any other comments?
Thanks
Xie Yisheng
On 2016/8/26 18:26, Will Deacon wrote:
> On Mon, Aug 22, 2016 at 09:20:02PM +0800, Xie Yisheng wrote:
>>
>> Xie Yisheng (2):
>> mm/hugetlb: Introduce ARCH_HAS_GIGANTIC_PAGE
>> arm64 Kconfig: Select gigantic page
>>
>
> I assume you plan to merge this via -mm/akpm, given that Catalin has
> acked the arm64 part?
>
Yes, however, it seems still not merged right now.
> Will
>
> .
>
--
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:[~2016-08-27 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 13:20 [RFC PATCH v3 0/2] arm64/hugetlb: enable gigantic page Xie Yisheng
2016-08-22 13:20 ` [RFC PATCH v3 1/2] mm/hugetlb: Introduce ARCH_HAS_GIGANTIC_PAGE Xie Yisheng
2016-08-22 13:44 ` Michal Hocko
2016-09-08 9:55 ` Naoya Horiguchi
2016-08-22 13:20 ` [RFC PATCH v3 2/2] arm64 Kconfig: Select gigantic page Xie Yisheng
2016-08-26 10:26 ` [RFC PATCH v3 0/2] arm64/hugetlb: enable " Will Deacon
2016-08-27 9:45 ` Yisheng Xie [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=ec6fd8e5-37df-d212-0247-6f9454eafb8e@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@intel.com \
--cc=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.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).