Re: [net/mm PATCH v2 0/3] Page fragment updates

2016-12-27 Thread David Miller
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

Re: [net/mm PATCH v2 0/3] Page fragment updates

2016-12-27 Thread Alexander Duyck
On Fri, Dec 23, 2016 at 9:50 AM, David Miller wrote: > From: Alexander Duyck > Date: Fri, 23 Dec 2016 09:16:39 -0800 > >> I tried to get in touch with Andrew about this fix but I haven't heard any >> reply to the email I sent out on Tuesday. The last comment I had from >> Andrew against v1 was "

Re: [net/mm PATCH v2 0/3] Page fragment updates

2016-12-23 Thread David Miller
From: Alexander Duyck Date: Fri, 23 Dec 2016 09:16:39 -0800 > I tried to get in touch with Andrew about this fix but I haven't heard any > reply to the email I sent out on Tuesday. The last comment I had from > Andrew against v1 was "Looks good to me. I have it all queued for post-4.9 > process

[net/mm PATCH v2 0/3] Page fragment updates

2016-12-23 Thread Alexander Duyck
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 pag