Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread Andrew Morton
On Fri, 21 Jun 2019 20:24:59 +0200 David Hildenbrand wrote: > @Qian Cai, unfortunately I can't reproduce. > > If you get the chance, it would be great if you could retry with > > diff --git a/drivers/base/memory.c b/drivers/base/memory.c > index 972c5336bebf..742f99ddd148 100644 > --- a/drivers

Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread Qian Cai
On Fri, 2019-06-21 at 20:24 +0200, David Hildenbrand wrote: > On 21.06.19 17:15, Qian Cai wrote: > > On Thu, 2019-06-20 at 20:31 +0200, David Hildenbrand wrote: > > > @Andrew: Only patch 1, 4 and 6 changed compared to v1. > > > > > > Some further cleanups around memory block devices. Especially, c

Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread David Hildenbrand
On 21.06.19 21:07, Qian Cai wrote: > On Fri, 2019-06-21 at 20:56 +0200, David Hildenbrand wrote: >> On 21.06.19 20:24, David Hildenbrand wrote: >>> On 21.06.19 17:15, Qian Cai wrote: On Thu, 2019-06-20 at 20:31 +0200, David Hildenbrand wrote: > @Andrew: Only patch 1, 4 and 6 changed compar

Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread Qian Cai
On Fri, 2019-06-21 at 20:56 +0200, David Hildenbrand wrote: > On 21.06.19 20:24, David Hildenbrand wrote: > > On 21.06.19 17:15, Qian Cai wrote: > > > On Thu, 2019-06-20 at 20:31 +0200, David Hildenbrand wrote: > > > > @Andrew: Only patch 1, 4 and 6 changed compared to v1. > > > > > > > > Some fur

Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread David Hildenbrand
On 21.06.19 20:24, David Hildenbrand wrote: > On 21.06.19 17:15, Qian Cai wrote: >> On Thu, 2019-06-20 at 20:31 +0200, David Hildenbrand wrote: >>> @Andrew: Only patch 1, 4 and 6 changed compared to v1. >>> >>> Some further cleanups around memory block devices. Especially, clean up >>> and simplify

Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread David Hildenbrand
On 21.06.19 17:15, Qian Cai wrote: > On Thu, 2019-06-20 at 20:31 +0200, David Hildenbrand wrote: >> @Andrew: Only patch 1, 4 and 6 changed compared to v1. >> >> Some further cleanups around memory block devices. Especially, clean up >> and simplify walk_memory_range(). Including some other minor cl

Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread David Hildenbrand
On 21.06.19 17:15, Qian Cai wrote: > On Thu, 2019-06-20 at 20:31 +0200, David Hildenbrand wrote: >> @Andrew: Only patch 1, 4 and 6 changed compared to v1. >> >> Some further cleanups around memory block devices. Especially, clean up >> and simplify walk_memory_range(). Including some other minor cl

Re: [PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-21 Thread Qian Cai
On Thu, 2019-06-20 at 20:31 +0200, David Hildenbrand wrote: > @Andrew: Only patch 1, 4 and 6 changed compared to v1. > > Some further cleanups around memory block devices. Especially, clean up > and simplify walk_memory_range(). Including some other minor cleanups. > > Compiled + tested on x86 wi

[PATCH v3 0/6] mm: Further memory block device cleanups

2019-06-20 Thread David Hildenbrand
@Andrew: Only patch 1, 4 and 6 changed compared to v1. Some further cleanups around memory block devices. Especially, clean up and simplify walk_memory_range(). Including some other minor cleanups. Compiled + tested on x86 with DIMMs under QEMU. Compile-tested on ppc64. v2 -> v3: - "mm/memory_ho