Received: by 10.192.165.148 with SMTP id m20csp2790704imm; Mon, 7 May 2018 00:53:35 -0700 (PDT) X-Google-Smtp-Source: AB8JxZraiMDV0W25ZNKOSorzPnRESvthVDdLhphJO35tO5rXSqLHuFWQUoslKYqVsKxP1NB4bbKO X-Received: by 10.98.31.3 with SMTP id f3mr32740323pff.213.1525679615168; Mon, 07 May 2018 00:53:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525679615; cv=none; d=google.com; s=arc-20160816; b=JS17P7hGddvn9Fmnmc+nggummzP5x2F0vsgdqsZPHlxuEC8h1r2sFl4256hrtdFIOF QrvqMVbo27p+HUjVz4oQLNp/JPbRETZMTvlRA5Pf64s2lAWN1tCmCf88x/xHng8xl6me lYASdqOH4tLg3PkVnjWNgz5wVwDMvk6mBBD3Z/gp7OtzIBSSg7dfN/V8bUK+Pnr1uNSV GHSvJR1wvXFHLEHgkSyyBWUudhEb7UyMp4Ohd+BDAIXSR3kPcIMxlwXSeurJI0R38/bW 8ogWwGY7H4PGBKLpnKT4ZEkpACtGCv4cAkzcnG3yAO2tAYkT6q/1ZMjLuIRa+xEsXWA6 ZTmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=+Ir1B/xMmPXXF5+FRJd2ZOXWNO3rq94wtaXSLbp0vOw=; b=cB0CDfOyibq9Uyw+5Ap+qrfJXZrjweqyX2PJgAYyaauChgEQCuVz8TselnLygTiIqM zwEs2AdxAob9wjeLHlU4vN0FyjFntzvaxBkODBst1i0P7t/BL26LikG6E4ZVDR+MxEti X5gRtorwYdRh/8g1NIv4GqbAKJZ6jOmmkQG3uqz2VxfdZFjupdbTucpNH8CVl+5jo3ni +BoxpsXmFz2OrnEbkFa489sOwUtg2gV2R3c7rQHZYmRhdv0uZCAJ75VqUCuwEyMT0gJ+ FseMTwwUwbvfTXG6SjA+IrABKa2QHrAqoF5x2UrsykAG7cYNchlbhqNxHDPG9uGyoWJs xgzA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w16-v6si8735673plq.141.2018.05.07.00.53.20; Mon, 07 May 2018 00:53:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751954AbeEGHxL (ORCPT + 99 others); Mon, 7 May 2018 03:53:11 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:55384 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751042AbeEGHxK (ORCPT ); Mon, 7 May 2018 03:53:10 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A8CFDF7FA2; Mon, 7 May 2018 07:53:09 +0000 (UTC) Received: from gondolin (dhcp-192-222.str.redhat.com [10.33.192.222]) by smtp.corp.redhat.com (Postfix) with ESMTP id A992C111F3B6; Mon, 7 May 2018 07:53:06 +0000 (UTC) Date: Mon, 7 May 2018 09:53:03 +0200 From: Cornelia Huck To: "dongbo (E)" Cc: , , , , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] vfio: fix documentation Message-ID: <20180507095303.450aef9b.cohuck@redhat.com> In-Reply-To: References: Organization: Red Hat GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Mon, 07 May 2018 07:53:09 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Mon, 07 May 2018 07:53:09 +0000 (UTC) for IP:'10.11.54.3' DOMAIN:'int-mx03.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'cohuck@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 7 May 2018 11:02:10 +0800 "dongbo (E)" wrote: > From: Dong Bo > > Update vfio_add_group_dev description to match the current API. > > Signed-off-by: Dong Bo > --- > Documentation/vfio.txt | 5 ++--- > 1 file changed, 2 insertions(+), 3 deletions(-) > > diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt > index ef6a511..f1a4d3c 100644 > --- a/Documentation/vfio.txt > +++ b/Documentation/vfio.txt > @@ -252,15 +252,14 @@ into VFIO core. When devices are bound and unbound to the driver, > the driver should call vfio_add_group_dev() and vfio_del_group_dev() > respectively:: > > - extern int vfio_add_group_dev(struct iommu_group *iommu_group, > - struct device *dev, > + extern int vfio_add_group_dev(struct device *dev, > const struct vfio_device_ops *ops, > void *device_data); > > extern void *vfio_del_group_dev(struct device *dev); > > vfio_add_group_dev() indicates to the core to begin tracking the > -specified iommu_group and register the specified dev as owned by > +iommu_group of the specified dev and register the dev as owned by > a VFIO bus driver. The driver provides an ops structure for callbacks > similar to a file operations structure:: > Reviewed-by: Cornelia Huck