[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZUAaiA0-FNRNy7wJ@google.com>
Date: Mon, 30 Oct 2023 14:05:12 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Paolo Bonzini <pbonzini@...hat.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 Tue, Oct 31, 2023, Stephen Rothwell wrote:
> Hi Paolo,
>
> On Mon, 30 Oct 2023 12:27:07 +0100 Paolo Bonzini <pbonzini@...hat.com> wrote:
> >
> > On 10/30/23 11:05, Christian Brauner wrote:
> > >
> > > @Paolo and @Sean, does that make sense and is the series for v6.7 or
> > > just already in -next for v6.8?
> >
> > It's for 6.8.
>
> Then it should not be in linux-next yet. :-(
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.
I assume -rc1 is when the floodgates "officially" open again?
Powered by blists - more mailing lists