From: Andrew Morton <akpm@linux-foundation.org>
To: Hillf Danton <hillf.zj@alibaba-inc.com>
Cc: 'Vaishali Thakkar' <vaishali.thakkar@oracle.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
'Mike Kravetz' <mike.kravetz@oracle.com>,
'Naoya Horiguchi' <n-horiguchi@ah.jp.nec.com>,
'Michal Hocko' <mhocko@suse.com>,
'Yaowei Bai' <baiyaowei@cmss.chinamobile.com>,
'Dominik Dingel' <dingel@linux.vnet.ibm.com>,
"'Kirill A. Shutemov'" <kirill.shutemov@linux.intel.com>,
'Paul Gortmaker' <paul.gortmaker@windriver.com>,
'Dave Hansen' <dave.hansen@linux.intel.com>,
'Chris Metcalf' <cmetcalf@ezchip.com>
Subject: Re: [PATCH 2/2] arch:mm: Use hugetlb_bad_size
Date: Wed, 23 Mar 2016 13:31:37 -0700 [thread overview]
Message-ID: <20160323133137.944775ef2e70a8a505aabd24@linux-foundation.org> (raw)
In-Reply-To: <0b0601d184ba$436808d0$ca381a70$@alibaba-inc.com>
On Wed, 23 Mar 2016 12:12:48 +0800 "Hillf Danton" <hillf.zj@alibaba-inc.com> wrote:
> >
> > Do you want me to send new version of the patchset breaking this patch in
> > to separate patches?
> >
> Yes.
That would be a bit of a pain because then each arch maintainer will
need to check that the [1/1] patch is merged. In fact the arch
maintainer can't actually merge the arch patch locally without having
[1/1] present.
Simply acking this patch would make life much simpler, please.
--
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-03-23 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 10:05 [PATCH 2/2] arch:mm: Use hugetlb_bad_size Vaishali Thakkar
2016-03-22 23:38 ` Naoya Horiguchi
2016-03-23 2:42 ` Mike Kravetz
2016-03-23 3:15 ` Hillf Danton
2016-03-23 3:55 ` Vaishali Thakkar
2016-03-23 4:12 ` Hillf Danton
2016-03-23 20:31 ` 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=20160323133137.944775ef2e70a8a505aabd24@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=cmetcalf@ezchip.com \
--cc=dave.hansen@linux.intel.com \
--cc=dingel@linux.vnet.ibm.com \
--cc=hillf.zj@alibaba-inc.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=paul.gortmaker@windriver.com \
--cc=vaishali.thakkar@oracle.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).