Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751525AbeADAF0 (ORCPT + 1 other); Wed, 3 Jan 2018 19:05:26 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:36208 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751014AbeADAFZ (ORCPT ); Wed, 3 Jan 2018 19:05:25 -0500 Date: Wed, 3 Jan 2018 16:05:23 -0800 From: Andrew Morton To: Michal Hocko Cc: , Mike Kravetz , Naoya Horiguchi , LKML Subject: Re: [PATCH 0/6] mm, hugetlb: allocation API and migration improvements Message-Id: <20180103160523.2232e3c2da1728c84b160d56@linux-foundation.org> In-Reply-To: <20180103093213.26329-1-mhocko@kernel.org> References: <20180103093213.26329-1-mhocko@kernel.org> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Wed, 3 Jan 2018 10:32:07 +0100 Michal Hocko wrote: > I've posted this as an RFC [1] and both Mike and Naoya seem to be OK > both with patches and the approach. I have rebased this on top of [2] > because there is a small conflict in mm/mempolicy.c. I know it is late > in the release cycle but similarly to [2] I would really like to see > this in linux-next for a longer time for a wider testing exposure. I'm interpreting this to mean "hold for 4.17-rc1"?