[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABgObfa_-BYrx0s=PAed=S2C-NgoCuvdYaVS_D9Fm6FxSChQNA@mail.gmail.com>
Date: Tue, 31 Oct 2023 14:42:49 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Sean Christopherson <seanjc@...gle.com>,
Christian Brauner <brauner@...nel.org>,
Ackerley Tng <ackerleytng@...gle.com>,
Chao Peng <chao.p.peng@...ux.intel.com>,
Isaku Yamahata <isaku.yamahata@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Michael Roth <michael.roth@....com>,
Yu Zhang <yu.c.zhang@...ux.intel.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kvm-x86 tree
On Mon, Oct 30, 2023 at 10:10 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi Sean,
>
> On Mon, 30 Oct 2023 14:05:12 -0700 Sean Christopherson <seanjc@...gle.com> wrote:
> >
> > That's my bad, I wanted to get the guest_memfd code exposure asap and jumped the
> > gun. I'll yank the branch out kvm-x86/next.
>
> Thanks.
In all fairness, it was only recently pushed back from 6.7 to 6.8 so
it probably would have made sense to include it _even earlier_. But I
agree that at this point it's better if we wait for 6.7-rc1 before it
makes it back into linux-next. At that point I'll include the conflict
resolution myself.
Paolo
Powered by blists - more mailing lists