On Fri, Mar 29, 2019 at 03:23:00PM -0700, John Hubbard wrote: > On 3/28/19 6:43 AM, Oscar Salvador wrote: > > Hi, > > > > since last two RFCs were almost unnoticed (thanks David for the feedback), > > I decided to re-work some parts to make it more simple and give it a more > > testing, and drop the RFC, to see if it gets more attention. > > I also added David's feedback, so now all users of add_memory/__add_memory/ > > add_memory_resource can specify whether they want to use this feature or not. > > I also fixed some compilation issues when CONFIG_SPARSEMEM_VMEMMAP is not set. > > > > Hi Oscar, say, what tree and/or commit does this series apply to? I'm having some > trouble finding the right place. Sorry for the easy question, I did try quite > a few trees already... Hi John, I somehow forgot to mention it in the cover-letter, sorry. This patchsed is based on v5.1-rc2-31-gece06d4a8149 + the following fixes on top: * https://patchwork.kernel.org/patch/10862609/ * https://patchwork.kernel.org/patch/10862611/ * https://patchwork.kernel.org/patch/10853049/ -- Oscar Salvador SUSE L3
