Re: [next PATCH v4 0/3] Page fragment updates

[Andrew Morton]

On Tue, 03 Jan 2017 18:38:48 -0800 Alexander Duyck <alexander.duyck@xxxxxxxxx> wrote:

> This patch series takes care of a few cleanups for the page fragments API.
> 
> First we do some renames so that things are much more consistent.  First we
> move the page_frag_ portion of the name to the front of the functions
> names.  Secondly we split out the cache specific functions from the other
> page fragment functions by adding the word "cache" to the name.
> 
> Finally I added a bit of documentation that will hopefully help to explain
> some of this.  I plan to revisit this later as we get things more ironed
> out in the near future with the changes planned for the DMA setup to
> support eXpress Data Path.
> 
> ---
> 
> v2: Fixed a comparison between a void* and 0 due to copy/paste from free_pages
> v3: Updated first rename patch so that it is just a rename and doesn't impact
>     the actual functionality to avoid performance regression.
> v4: Fix mangling that occured due to a bad merge fix when patches 1 and 2
>     were swapped and then swapped back.
> 
> I'm submitting this to Intel Wired Lan and Jeff Kirsher's "next-queue" for
> acceptance as I have a series of other patches for igb that are blocked by
> by these patches since I had to rename the functionality fo draining extra
> references.
> 
> This series was going to be accepted for mmotm back when it was v1, however
> since then I found a few minor issues that needed to be fixed.
> 
> I am hoping to get an Acked-by from Andrew Morton for these patches and
> then have them submitted to David Miller as he has said he will accept them
> if I get the Acked-by.  In the meantime if these can be applied to
> next-queue while waiting on that Acked-by then I can submit the other
> patches for igb and ixgbe for testing.

The patches look fine.  How about I just scoot them straight into
mainline next week?  I do that occasionally, just to simplify ongoing
development and these patches are safe enough.