From: David Miller <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
Date: Tue, 27 Dec 2016 13:55:28 -0500 (EST) [thread overview]
Message-ID: <20161227.135528.1940863604492112350.davem@davemloft.net> (raw)
In-Reply-To: <CAKgT0UeP3QkjPQcPGv4ONhO5D56-+TL=-JYx6R+YJvLcCgK3cw@mail.gmail.com>
From: Alexander Duyck <alexander.duyck@gmail.com>
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.
prev parent reply other threads:[~2016-12-27 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 17:16 [net/mm PATCH v2 0/3] Page fragment updates Alexander Duyck
2016-12-23 17:17 ` [net/mm PATCH v2 1/3] mm: Rename __alloc_page_frag to page_frag_alloc and __free_page_frag to page_frag_free Alexander Duyck
2016-12-23 17:17 ` [net/mm PATCH v2 2/3] mm: Rename __page_frag functions to __page_frag_cache, drop order from drain Alexander Duyck
2016-12-23 17:17 ` [net/mm PATCH v2 3/3] mm: Add documentation for page fragment APIs Alexander Duyck
2016-12-23 17:50 ` [net/mm PATCH v2 0/3] Page fragment updates David Miller
2016-12-27 18:54 ` Alexander Duyck
2016-12-27 18:55 ` David Miller [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=20161227.135528.1940863604492112350.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@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).