Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp621112pxb; Fri, 22 Apr 2022 08:03:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwKUqlWbg+L+T6f2NNp2cPBwlsUMmSU7f5G+BgMOg9MNnInMuDnrlpwhxi4xdV7bgp0qrGn X-Received: by 2002:a17:906:7c93:b0:6cd:341a:a1d5 with SMTP id w19-20020a1709067c9300b006cd341aa1d5mr4434418ejo.698.1650639794574; Fri, 22 Apr 2022 08:03:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650639794; cv=none; d=google.com; s=arc-20160816; b=Kwp8QbYs9HDeew5d8DgRwpGJUiig5Mch7yYQeM/t/xgd/QJK18+l7mTIunkSZbaCvV ktqMSM0jujAzyTsUL6ADTayRhzly7+X/XApPqXp3f9CmkQcJcuhlq0BIHxt0H8GwFbcz YKBy1wjD3ukxW0LF4eVPrJTurxkJWR9rr77e9kYFseRQ8G0DK484pUr0ErrBWh0r1Btu qykeR37E512sUYS0lAl+csDuUvdyEAUDCv6XAci2FntQ182LDYJwZT0ZApjv8h2rN9hA 1GhiqBBycWhb4YEYl7MbNAzNf1arZr0TQHQgLxIVqDLNEf7llzB9UZEfUVd7oc4TwJ2U TOvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=qDasHStL3WbtX/WC6w4mtbNUgnFA9c/gnJltufAWKVg=; b=rlL99H/7IDQ9jQNHeiXeRKspiwFqXo039NZaNLlAdU7EsweVTUg0OJksvR5yMkPNra Ntb9gfzs0X4NcXbhAeIJfgyEu1MulZXTP/9olp8byTyKySBcv/Hml07yppO6HbmoShoW 5qXrMqDHNbedELp5TrEQRKjWlsIEL8SuioMbFEjbHEmdaDxoffrEU9jvQOFQdbORCZRt b9BtSYuGr3TLLBIgIAyzWtTcQSlMOLHGSlpaJ6zAPO+nl/aAAltaQjhmL4GK7Invg/bQ YNvDwzn1Kp8k2ZlFzuthSJPqe99eTTgtZH/6EQa9dflXkBS0gEJwnJrdptEi5uPHCqK2 CvWA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e21-20020a056402331500b00421af4941a8si6438788eda.249.2022.04.22.08.02.48; Fri, 22 Apr 2022 08:03:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1384538AbiDUFud (ORCPT + 99 others); Thu, 21 Apr 2022 01:50:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41692 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1384548AbiDUFub (ORCPT ); Thu, 21 Apr 2022 01:50:31 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3AC161208F for ; Wed, 20 Apr 2022 22:47:42 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 9154768B05; Thu, 21 Apr 2022 07:47:38 +0200 (CEST) Date: Thu, 21 Apr 2022 07:47:38 +0200 From: Christoph Hellwig To: "Wang, Zhi A" Cc: Jason Gunthorpe , Alex Williamson , Jani Nikula , Joonas Lahtinen , "Vivi, Rodrigo" , Christoph Hellwig , "intel-gfx@lists.freedesktop.org" , "intel-gvt-dev@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , Zhenyu Wang Subject: Re: [PULL v2] gvt-next Message-ID: <20220421054738.GA20772@lst.de> References: <5a8b9f48-2c32-8177-1c18-e3bd7bfde558@intel.com> <20220420164351.GC2120790@nvidia.com> <20220420114033.7f8b57c7.alex.williamson@redhat.com> <20220420174600.GD2120790@nvidia.com> <20220420200034.GE2120790@nvidia.com> <55cb46db-754e-e339-178c-0a2cfaf65810@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55cb46db-754e-e339-178c-0a2cfaf65810@intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 21, 2022 at 04:57:34AM +0000, Wang, Zhi A wrote: > Is it possible that I can send two different pull based on the same branch? > I was thinking I can remove this line in the original patch and then add a > small patch to add this line back on the top. Then make two different tags > before and after that small patch, send one pull with tag that includes that > small patch to i915 and the other pull with tag that doesn't includes it to > VFIO? Yes, you can do that as long as the small fixup commit is the very last one.