[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <908a906c-b2db-ce02-8432-649dcfd8d6a4@redhat.com>
Date: Wed, 17 Apr 2019 09:44:13 +0200
From: David Hildenbrand <david@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Oscar Salvador <osalvador@...e.de>,
Michal Hocko <mhocko@...e.com>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Wei Yang <richard.weiyang@...il.com>, Qian Cai <cai@....pw>,
Arun KS <arunks@...eaurora.org>,
Mathieu Malaterre <malat@...ian.org>
Subject: Re: [PATCH v1 1/4] mm/memory_hotplug: Release memory resource after
arch_remove_memory()
On 17.04.19 05:37, Andrew Morton wrote:
> On Wed, 10 Apr 2019 10:07:24 +0200 David Hildenbrand <david@...hat.com> wrote:
>
>> Care to fixup both u64 to resource_size_t? Or should I send a patch?
>> Whatever you prefer.
>
> Please send along a fixup.
Will do!
>
> This patch series has no evidence of having been reviewed :(. Can you
> suggest who could help us out here?
Usually I would say Oscar and Michal, but they seem to be fairly busy. I
guess only the first patch is a real change, the other three patches are
mostly function prototype changes, handling errors in a nicer way.
Thanks!
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists