From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolai Stange Subject: Re: [PATCH v2 1/2] x86/efi: don't allocate memmap through memblock after mm_init() Date: Thu, 05 Jan 2017 13:53:50 +0100 Message-ID: <87pok1hdlt.fsf@gmail.com> References: <20161222102340.2689-1-nicstange@gmail.com> <20161223145206.GC16838@codeblueprint.co.uk> <878tr6jqoa.fsf@gmail.com> <20170105074221.GA1777@gmail.com> <87inpt6ce7.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Ard Biesheuvel's message of "Thu, 5 Jan 2017 11:34:06 +0000") Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Ard Biesheuvel Cc: Nicolai Stange , Ingo Molnar , Matt Fleming , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "x86@kernel.org" , "linux-efi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Mika =?utf-8?Q?Penttil=C3=A4?= , Dan Williams List-Id: linux-efi@vger.kernel.org Ard Biesheuvel writes: > On 5 January 2017 at 10:15, Nicolai Stange wrote: >> So, are you Ok with only taking the other review comment, namely >> >> "modify efi_fake_memmap() to use your new efi_memmap_alloc() function >> for consistency" >> >> into account for a v3? >> > > Yes, that should be sufficient for a fix that can be backported. > Anything else can wait for now Ard, thanks for your help! v3 is here: http://lkml.kernel.org/r/20170105125130.2815-1-nicstange-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Nicolai