From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 39913C4167B for ; Mon, 30 Oct 2023 21:05:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231868AbjJ3VFS (ORCPT ); Mon, 30 Oct 2023 17:05:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36588 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231817AbjJ3VFQ (ORCPT ); Mon, 30 Oct 2023 17:05:16 -0400 Received: from mail-pl1-x649.google.com (mail-pl1-x649.google.com [IPv6:2607:f8b0:4864:20::649]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A08E2DD for ; Mon, 30 Oct 2023 14:05:14 -0700 (PDT) Received: by mail-pl1-x649.google.com with SMTP id d9443c01a7336-1cc252cbde2so21071365ad.0 for ; Mon, 30 Oct 2023 14:05:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1698699914; x=1699304714; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=J/ro39ZjXP8/N78CP33HQRu7jBM2jc66Dx/aqxCDkow=; b=yNb2sQJSa3cI8AsqaWI3Mrv+uTPvMgLn41PACq9M4XHIHX5Av6cI3Q1axxst85oiiy sKqvnZsVeSb7z1TyqesaT7boFrfb68me94Ri9ajdl8Tl4VVliq70kINgSVEZ5lYbLej+ QNdSkkNjiH33g4c4QpsNwLEiijjATGzq4VygpyWEktbOSCSAuH21hmgYeOuXgLg7JBuJ hlmdL2vVPyanck/Q0aOFdF1ZMlmYQmcaEJJPUH8RbFNLfQJwuOkHXavtiOOXKLQ6XSK2 311ZxVezEp8T+frJ6FNPmNx9NV/jOLAOmoSQYsgWttqyG6f9uHTIsXS+T+2n4wiwX5xy XNsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698699914; x=1699304714; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=J/ro39ZjXP8/N78CP33HQRu7jBM2jc66Dx/aqxCDkow=; b=XkuKmbg0qIewJYWM7yOaKtTvcaChkzI/HsTxv8RQqLCLg/NOd3G4yZQmwZby9VLz65 Df9a8y/Fs3aRFnNbux/AsRnW9eDAjHlbHbszbq6QcVpLh/Dq0hvuosylEGiDmeqGcUNS 6LEX2IUs205U2SW9iOkh/3Sw2DTj7El3iXLZYSvImln64Rpq8psxXaApvK5Q1Fh55c8K q3XO62uOHHqBQOI1Z714oflyaEepsc7iBLFgcsV+sCW2v0FsSQTFzqXR+EXKSOt3NgpA 59FfnT9zd+i4r4C22WfobIEB9JPFQ09EqyaWWksCA+IeJtCyk9VW+qRYvRtW3mP9iXIJ vRXQ== X-Gm-Message-State: AOJu0YxNp75BFRv3rKtvhVpF5woL6GtK1Fo1AUbazxnwMs2AnaIH5x8j Nc5XyppjzwXloLIgEfd2CtubKCrzMMo= X-Google-Smtp-Source: AGHT+IGz83OREeKaWujSJspphjF2KmSJNNXI/EohopzNL13Ec4YlnBVRNnbTbb4QwnzljOjGofBO2NtSs5E= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:902:efcc:b0:1cc:2bd6:b54a with SMTP id ja12-20020a170902efcc00b001cc2bd6b54amr157500plb.10.1698699914172; Mon, 30 Oct 2023 14:05:14 -0700 (PDT) Date: Mon, 30 Oct 2023 14:05:12 -0700 In-Reply-To: <20231031073705.512dab4b@canb.auug.org.au> Mime-Version: 1.0 References: <20231030134806.24510492@canb.auug.org.au> <20231030-ignorant-liebschaft-6d603ab43494@brauner> <3ed75fa4-6b49-4fd2-a907-8619ca19a8b8@redhat.com> <20231031073705.512dab4b@canb.auug.org.au> Message-ID: Subject: Re: linux-next: build failure after merge of the kvm-x86 tree From: Sean Christopherson To: Stephen Rothwell Cc: Paolo Bonzini , Christian Brauner , Ackerley Tng , Chao Peng , Isaku Yamahata , "Kirill A. Shutemov" , Michael Roth , Yu Zhang , Linux Kernel Mailing List , Linux Next Mailing List Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 31, 2023, Stephen Rothwell wrote: > Hi Paolo, > > On Mon, 30 Oct 2023 12:27:07 +0100 Paolo Bonzini 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?