Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp1816837pxb; Mon, 12 Apr 2021 07:25:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyRBp6AS3C4/22Ays4R7oDvENKVWHPW0d63Ogv4k5RwBur/Xs7ClWYrCYZr5RuvoCyz9DY/ X-Received: by 2002:a05:6402:30ae:: with SMTP id df14mr29286590edb.97.1618237516904; Mon, 12 Apr 2021 07:25:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618237516; cv=none; d=google.com; s=arc-20160816; b=Z4VmZHALkYsQVqRtWogvi47jRv9u9ceppo1yCpWVk7ejsa+ExupVZ0X9S9rE/inmT7 fYHDMP6HYzPO+SmazR2TErZxEhah01dJi1q+gjE1C4lDTSZ2owdk5UeMSKQEbCnq8yz4 12J8BlTNxALQEy7Cwg5VhbKuNW8fUXigoSAehZfgYZZMlY/tEw9AnFNV1XNfAWG4hydV oqes+0Tq6ompMoGk7pKrNwm2DEujYSZlZKLbGxCQM4ZToKpsTKGyzUqCsWUwuhZfJ/GD QWIMtknMts+4Uvd08t+brymE4V+QGfTb/tJTiYKrF6zn5kuNbSM+V+IsU+r1RxCFnuXJ cF2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=GrF4YEmMpBSr4tpcoU2zsLDVhSyzm4Z4HeHxtyh0vvU=; b=kYBLklJOh/78Mw4BPpCNrxXhPyVJIcjOeR5yxSstCOx4nIuNZUZjm86uz1P2CX3vwl xZ16vZW1JcrkU8jGsn1cn7fZgZUNtxH8tiPFQYi0rMD40VGs8dM2wluwTU9ulMu2s+Xt /+FicF5/m8/z5/mWtASCmb6qEuGANYAL7ydzHMnxHrSe+oWN2o3rAEjX90EbzI++y/7E hqAqaypn+g33WYdyJy4fIWfR6lRtRw4V+WikzY8LiT7GXieUSFGHUoyfYJIwlZ9CMfkH cNfTQKW2tGU4IUiT/chGhEINYtj3KtpHzhm8eAxq88Wxqo+McTEEVitpt9HAOICzmk1+ eZXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Wrzpc5AV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h15si8194489ejq.438.2021.04.12.07.24.49; Mon, 12 Apr 2021 07:25:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Wrzpc5AV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239428AbhDLOXg (ORCPT + 99 others); Mon, 12 Apr 2021 10:23:36 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:45405 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237789AbhDLOXf (ORCPT ); Mon, 12 Apr 2021 10:23:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1618237397; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GrF4YEmMpBSr4tpcoU2zsLDVhSyzm4Z4HeHxtyh0vvU=; b=Wrzpc5AVq5jGyuzokVFFNTzCHjxkb5yrBwZQ3dIOqKKdK1gvknDr/poDCncyRlkSg71zgN CAkOqb3C+GDglwQxraJPVOfa5GdTyG8ORtXxrL/s2a3PR8sGHu5EQ/ZpJYEvB9AFFPFgDo pXRc3i7sfKXVW+gOlupS3A7hH0hMziw= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-197-OL_3aR56Mdyv0DeVj_LUSg-1; Mon, 12 Apr 2021 10:23:12 -0400 X-MC-Unique: OL_3aR56Mdyv0DeVj_LUSg-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 52AFC10054F6; Mon, 12 Apr 2021 14:23:08 +0000 (UTC) Received: from omen (ovpn-117-254.rdu2.redhat.com [10.10.117.254]) by smtp.corp.redhat.com (Postfix) with ESMTP id E97905D9DE; Mon, 12 Apr 2021 14:23:04 +0000 (UTC) Date: Mon, 12 Apr 2021 08:23:04 -0600 From: Alex Williamson To: Michael Ellerman Cc: Christoph Hellwig , Benjamin Herrenschmidt , Greg Kroah-Hartman , Jason Gunthorpe , David Airlie , Daniel Vetter , dri-devel@lists.freedesktop.org, Paul Mackerras , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH 1/2] vfio/pci: remove vfio_pci_nvlink2 Message-ID: <20210412082304.5e7c0a80@omen> In-Reply-To: <87y2dndelm.fsf@mpe.ellerman.id.au> References: <20210326061311.1497642-1-hch@lst.de> <20210326061311.1497642-2-hch@lst.de> <20210406133805.715120bd@omen> <87y2dndelm.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 12 Apr 2021 19:41:41 +1000 Michael Ellerman wrote: > Alex Williamson writes: > > On Fri, 26 Mar 2021 07:13:10 +0100 > > Christoph Hellwig wrote: > > > >> This driver never had any open userspace (which for VFIO would include > >> VM kernel drivers) that use it, and thus should never have been added > >> by our normal userspace ABI rules. > >> > >> Signed-off-by: Christoph Hellwig > >> Acked-by: Greg Kroah-Hartman > >> --- > >> drivers/vfio/pci/Kconfig | 6 - > >> drivers/vfio/pci/Makefile | 1 - > >> drivers/vfio/pci/vfio_pci.c | 18 - > >> drivers/vfio/pci/vfio_pci_nvlink2.c | 490 ---------------------------- > >> drivers/vfio/pci/vfio_pci_private.h | 14 - > >> include/uapi/linux/vfio.h | 38 +-- > >> 6 files changed, 4 insertions(+), 563 deletions(-) > >> delete mode 100644 drivers/vfio/pci/vfio_pci_nvlink2.c > > > > Hearing no objections, applied to vfio next branch for v5.13. Thanks, > > Looks like you only took patch 1? > > I can't take patch 2 on its own, that would break the build. > > Do you want to take both patches? There's currently no conflicts against > my tree. It's possible one could appear before the v5.13 merge window, > though it would probably just be something minor. > > Or I could apply both patches to my tree, which means patch 1 would > appear as two commits in the git history, but that's not a big deal. I've already got a conflict in my next branch with patch 1, so it's best to go through my tree. Seems like a shared branch would be easiest to allow you to merge and manage potential conflicts against patch 2, I've pushed a branch here: https://github.com/awilliam/linux-vfio.git v5.13/vfio/nvlink Thanks, Alex