On Thu, Jun 11, 2020 at 01:33:04PM +0200, David Hildenbrand wrote: > > > Am 11.06.2020 um 13:18 schrieb Michael S. Tsirkin <mst@xxxxxxxxxx>: > > > On Thu, Jun 11, 2020 at 01:00:24PM +0200, David Hildenbrand wrote: > > I'd like to have this patch in 5.8, with the initial merge of > virtio-mem > > if possible (so the user space representation of virtio-mem > added memory > > resources won't change anymore). > > > > So my plan is to rebase on top of -rc1 and merge this for rc2 then. > > I don't like rebase on top of tip as the results are sometimes kind > of > > random. > > > > Right, I just wanted to get this out early so we can discuss how to > proceed. > > > > And let's add a Fixes: tag as well, this way people will remember > to > > pick this. > > Makes sense? > > > > Yes, it's somehow a fix (for kexec). So > > > > Fixes: 5f1f79bbc9e26 ("virtio-mem: Paravirtualized memory hotplug") > > > > I can respin after -rc1 with the commit id fixed as noted by Pankaj. > > Just let me know what you prefer. > > > > Thanks! > > > Some once this commit is in Linus' tree, please ping me. > > > It already is as mentioned, only the id was wrong. > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id= > 7b7b27214bba1966772f9213cd2d8e5d67f8487f OK I pushed this into next based on tip. Let's see what happens. > > > > -- > > Thanks, > > > > David / dhildenb > > > _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization