Re: [PATCH 3.18 093/185] microblaze: switch to NO_BOOTMEM

2018-05-29 Thread Michal Simek
On 29.5.2018 16:34, Rob Herring wrote: > On Mon, May 28, 2018 at 5:02 AM, Greg Kroah-Hartman > wrote: >> 3.18-stable review patch. If anyone has any objections, please let me know. >> >> -- >> >> From: Rob Herring >> >> [ Upstream commit 101646a24a2f9cdb61d7732459fbf068a7bbb542 ]

Re: [PATCH 3.18 093/185] microblaze: switch to NO_BOOTMEM

2018-05-29 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 09:34:33AM -0500, Rob Herring wrote: > On Mon, May 28, 2018 at 5:02 AM, Greg Kroah-Hartman > wrote: > > 3.18-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Rob Herring > > > > [ Upstream commit 101646a24a2f9

Re: [PATCH 3.18 093/185] microblaze: switch to NO_BOOTMEM

2018-05-29 Thread Rob Herring
On Mon, May 28, 2018 at 5:02 AM, Greg Kroah-Hartman wrote: > 3.18-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Rob Herring > > [ Upstream commit 101646a24a2f9cdb61d7732459fbf068a7bbb542 ] > > Microblaze doesn't set CONFIG_NO_BOOTMEM and

[PATCH 3.18 093/185] microblaze: switch to NO_BOOTMEM

2018-05-28 Thread Greg Kroah-Hartman
3.18-stable review patch. If anyone has any objections, please let me know. -- From: Rob Herring [ Upstream commit 101646a24a2f9cdb61d7732459fbf068a7bbb542 ] Microblaze doesn't set CONFIG_NO_BOOTMEM and so memblock_virt_alloc() doesn't work for CONFIG_HAVE_MEMBLOCK && !CONFIG_