[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <86ecswewjs.wl-maz@kernel.org>
Date: Wed, 27 Aug 2025 14:14:31 +0100
From: Marc Zyngier <maz@...nel.org>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Sean Christopherson <seanjc@...gle.com>,
Oliver Upton <oliver.upton@...ux.dev>,
kvm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Ira Weiny <ira.weiny@...el.com>,
Gavin Shan <gshan@...hat.com>,
Shivank Garg <shivankg@....com>,
Vlastimil Babka <vbabka@...e.cz>,
Xiaoyao Li <xiaoyao.li@...el.com>,
David Hildenbrand <david@...hat.com>,
Fuad Tabba <tabba@...gle.com>,
Ackerley Tng <ackerleytng@...gle.com>,
Tao Chan <chentao@...inos.cn>,
James Houghton <jthoughton@...gle.com>
Subject: Re: [PATCH v17 00/24] KVM: Enable mmap() for guest_memfd
On Wed, 27 Aug 2025 14:11:22 +0100,
Paolo Bonzini <pbonzini@...hat.com> wrote:
>
> Yo can
>
> On Wed, Aug 27, 2025 at 3:08 PM Marc Zyngier <maz@...nel.org> wrote:
> >
> > On Wed, 27 Aug 2025 09:43:54 +0100,
> > Paolo Bonzini <pbonzini@...hat.com> wrote:
> > > Applied to kvm/next, thanks!
> >
> > Can you please create a stable branch for these patches? It is quite
> > likely that whatever I queue for 6.18 will conflict with that, and I'd
> > like to be able to resolve the conflicts myself.
>
> You can just base kvm-arm/next on kvm/next, but if you prefer I pushed
> guest-memfd-mmap at https://git.kernel.org/pub/scm/virt/kvm/kvm.git/.
Pulled, thanks.
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists