Please do not top-post On Wed 24-10-18 09:12:52, Marc Orr wrote: > No. I separated them because they're going to two different subsystems > (i.e., mm and kvm). Yes, they do go to two different subsystems but they would have to coordinate for the final merge because the later wouldn't work without the former. So it is easier to have them in a single tree. From the review POV it is better to have them in the single patch to see the usecase for the export and judge whether this is the best option. > I'll fold them and resend the patch. Thanks! > On Wed, Oct 24, 2018 at 7:16 AM Michal Hocko <mhocko@xxxxxxxxxx> wrote: > > > > On Tue 23-10-18 17:10:55, Marc Orr wrote: > > > Ack. The user is the 2nd patch in this series, the kvm_intel module, > > > which uses this version of vmalloc() to allocate vcpus across > > > non-contiguous memory. I will cc everyone here on that 2nd patch for > > > context. > > > > Is there any reason to not fold those two into a single one? > > -- > > Michal Hocko > > SUSE Labs -- Michal Hocko SUSE Labs
