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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E2371C433EF for ; Mon, 11 Oct 2021 09:48:46 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id ABE4160D07 for ; Mon, 11 Oct 2021 09:48:46 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org ABE4160D07 Authentication-Results: mail.kernel.org; dmarc=pass (p=none dis=none) header.from=xenproject.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.205653.361021 (Exim 4.92) (envelope-from ) id 1mZrvB-0007FR-5D; Mon, 11 Oct 2021 09:48:37 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 205653.361021; Mon, 11 Oct 2021 09:48:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mZrvB-0007FK-2R; Mon, 11 Oct 2021 09:48:37 +0000 Received: by outflank-mailman (input) for mailman id 205653; Mon, 11 Oct 2021 09:48:36 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mZrvA-0007F7-4X for xen-devel@lists.xenproject.org; Mon, 11 Oct 2021 09:48:36 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mZrvA-00023T-1a for xen-devel@lists.xenproject.org; Mon, 11 Oct 2021 09:48:36 +0000 Received: from iwj (helo=mariner.uk.xensource.com) by xenbits.xenproject.org with local-bsmtp (Exim 4.92) (envelope-from ) id 1mZrvA-0001GX-0V for xen-devel@lists.xenproject.org; Mon, 11 Oct 2021 09:48:36 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.89) (envelope-from ) id 1mZrv6-0000eQ-7m; Mon, 11 Oct 2021 10:48:32 +0100 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xenproject.org; s=20200302mail; h=References:In-Reply-To:Subject:Cc:To:Date :Message-ID:Content-Transfer-Encoding:Content-Type:MIME-Version:From; bh=Ng3hqqfwgfFQ/6WKuuXxllUNR+zKFeMHWw3MTOYoe8E=; b=RTbfTOrSUmN81cWzAXtyOuYezf VlfwaoTaQ7Rh5EUYJWN4nnRuCT25ypyq0P3Ej6x93D+eLPymXcOxvvSLTctOgzJHLLG4dvlfqkMjS lUlkKmumRH3q2hGbsG+Sj0F2cfyIRWiar+Ue2Q7zDzTcjfp5RyuGbp04vgpDFQJd9WE0=; From: Ian Jackson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <24932.2159.627949.196364@mariner.uk.xensource.com> Date: Mon, 11 Oct 2021 10:48:31 +0100 To: Rahul Singh Cc: , Andrew Cooper , , , Christian Lindig , David Scott , Ian Jackson , Wei Liu , George Dunlap , Jan Beulich , Julien Grall , Stefano Stabellini , Volodymyr Babchuk , Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: [PATCH v5 07/11] xen/domctl: Introduce XEN_DOMCTL_CDF_vpci flag In-Reply-To: <548fa153-b2e3-7f91-c7c9-a569e13b5809@citrix.com> References: <20d5b9d6a0d01a7b90711d28cbefb5701a88b438.1633540842.git.rahul.singh@arm.com> <548fa153-b2e3-7f91-c7c9-a569e13b5809@citrix.com> X-Mailer: VM 8.2.0b under 24.5.1 (i686-pc-linux-gnu) Andrew Cooper writes ("Re: [PATCH v5 07/11] xen/domctl: Introduce XEN_DOMCTL_CDF_vpci flag"): > Ian, for the 4.16 release, this series either needs completing with the > additional flag implemented, or this patch needs reverting to avoid us > shipping a broken interface. I have caught up on this thread. I think (hope?) it's converging. If not please let me know and maybe I can help. Can I ask to please be CC'd on the whole series for the patch(es) to sort this out. Please also make sure that those who commented are CC'd. I want the fixes that ultimately get committed to be the final fixes (probably that means they should have consensus). FTAOD, from a formal release management point of view: I regard those putative fixes as bugfixes so they can go in after the feature freeze (which is this Friday). But if suitable fixes don't make it in within the first few weeks of the freeze (and, as I expect, the maintainers or I still regard this as an RC bug) then a revert of the new feature will be the only option. Ian.