Re: [PATCH v2 0/9] mm: PG_reserved cleanups and documentation

2019-01-21 Thread David Hildenbrand
On 14.01.19 13:58, David Hildenbrand wrote: > Nothing major changed since the last version. I would be happy about > additional ACKs. If there are no further comments, can this go via the > mm-tree in one chunk? For the time being, I will not add further patches to this series (as discussed in res

Re: [PATCH v2 0/9] mm: PG_reserved cleanups and documentation

2019-01-15 Thread David Hildenbrand
On 15.01.19 16:38, Christoph Hellwig wrote: > On Mon, Jan 14, 2019 at 01:58:54PM +0100, David Hildenbrand wrote: >> Nothing major changed since the last version. I would be happy about >> additional ACKs. If there are no further comments, can this go via the >> mm-tree in one chunk? >> >> I was rec

Re: [PATCH v2 0/9] mm: PG_reserved cleanups and documentation

2019-01-15 Thread Christoph Hellwig
On Mon, Jan 14, 2019 at 01:58:54PM +0100, David Hildenbrand wrote: > Nothing major changed since the last version. I would be happy about > additional ACKs. If there are no further comments, can this go via the > mm-tree in one chunk? > > I was recently going over all users of PG_reserved. Short s

[PATCH v2 0/9] mm: PG_reserved cleanups and documentation

2019-01-14 Thread David Hildenbrand
Nothing major changed since the last version. I would be happy about additional ACKs. If there are no further comments, can this go via the mm-tree in one chunk? I was recently going over all users of PG_reserved. Short story: it is difficult and sometimes not really clear if setting/checking for