From: Sean Christopherson <seanjc@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Ackerley Tng <ackerleytng@google.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Michael Roth <michael.roth@amd.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the kvm-x86 tree
Date: Mon, 30 Oct 2023 14:05:12 -0700 [thread overview]
Message-ID: <ZUAaiA0-FNRNy7wJ@google.com> (raw)
In-Reply-To: <20231031073705.512dab4b@canb.auug.org.au>
On Tue, Oct 31, 2023, Stephen Rothwell wrote:
> Hi Paolo,
>
> On Mon, 30 Oct 2023 12:27:07 +0100 Paolo Bonzini <pbonzini@redhat.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?
next prev parent reply other threads:[~2023-10-30 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 2:48 linux-next: build failure after merge of the kvm-x86 tree Stephen Rothwell
2023-10-30 10:05 ` Christian Brauner
2023-10-30 11:27 ` Paolo Bonzini
2023-10-30 20:37 ` Stephen Rothwell
2023-10-30 21:05 ` Sean Christopherson [this message]
2023-10-30 21:10 ` Stephen Rothwell
2023-10-31 13:42 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2026-09-16 13:33 Mark Brown
2026-09-16 14:04 ` Sean Christopherson
2026-09-16 14:24 ` Mark Brown
2026-09-16 16:36 ` Oliver Upton
2026-09-16 16:43 ` Sean Christopherson
2026-09-16 16:44 ` Oliver Upton
2023-04-11 4:00 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZUAaiA0-FNRNy7wJ@google.com \
--to=seanjc@google.com \
--cc=ackerleytng@google.com \
--cc=brauner@kernel.org \
--cc=chao.p.peng@linux.intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=yu.c.zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.