From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756044AbcL0Sze (ORCPT ); Tue, 27 Dec 2016 13:55:34 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:44616 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753749AbcL0Szc (ORCPT ); Tue, 27 Dec 2016 13:55:32 -0500 Date: Tue, 27 Dec 2016 13:55:28 -0500 (EST) Message-Id: <20161227.135528.1940863604492112350.davem@davemloft.net> To: alexander.duyck@gmail.com Cc: linux-mm@kvack.org, akpm@linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, jeffrey.t.kirsher@intel.com Subject: Re: [net/mm PATCH v2 0/3] Page fragment updates From: David Miller In-Reply-To: References: <20161223170756.14573.74139.stgit@localhost.localdomain> <20161223.125053.1340469257610308679.davem@davemloft.net> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 27 Dec 2016 09:56:17 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Alexander Duyck Date: Tue, 27 Dec 2016 10:54:14 -0800 > Dave, I was wondering if you would be okay with me trying to push the > three patches though net-next. I'm thinking I might scale back the > first patch so that it is just a rename instead of making any > functional changes. The main reason why I am thinking of trying to > submit through net-next is because then I can then start working on > submitting the driver patches for net-next. Otherwise I'm looking at > this set creating a merge mess since I don't see a good way to push > the driver changes without already having these changes present. > > I'll wait until Andrew can weigh in on the patches before > resubmitting. My thought was to get an Acked-by from him and then see > if I can get them accepted into net-next. That way there isn't any > funky cross-tree merging that will need to go on, and it shouldn't > really impact the mm tree all that much as the only consumers for the > page frag code are the network stack anyway. I'm fine with this plan.