Received: by 10.192.165.148 with SMTP id m20csp4097481imm; Mon, 30 Apr 2018 11:40:18 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqvyAk19eLCrm8QCslIfI3Dxpm8dtQm1X0VhqOCvZxT0Hde6BYrQZr6PbSLWT0S1nOD29RQ X-Received: by 2002:a17:902:b492:: with SMTP id y18-v6mr13366204plr.2.1525113618934; Mon, 30 Apr 2018 11:40:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525113618; cv=none; d=google.com; s=arc-20160816; b=eRZfCgFhHqQr539rHynnOOXPPRtlucBpQsPdN9s7MwxpZ5y8AQyvWVq2IINyb6+JaS UOBMAPCd07hrksSOY1Oypt8WoyLHvnzeTI9hSO2O8SNp+yKP+NWoNoPHY6PhBlqt2VV1 GwH0tDfbqlbCvECMnaQ3dY81eRFsMVgTsMVoKLbgc0BfPPfyZwip8HU7VAcu/WNy51CC NRDqkyLjwhcojJTRLTWfPopcWSZCMEfATusVOJ4V1Gwsa7Vs8k/o4iL+4xUv9/wc3h1f 9luJ2FmbFFktti7Ifup4Db8NhXKaqflu4LdaFHeYw7W/m+x81Mk13cm16q+Ej+h+gcmz PCgQ== 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 :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=4XS8E9XeLCErwzh5BZDzCVbwHYke+q7VshBPUO4u/6o=; b=C5faO9mjq/CF3FXLw2UaDUMgDuX88rMwmLWEJejraZjMwpKeD0UHvrpdoYiv5Thb4S WRGcI/nJoQ0W47SRrnyXFttmR9eS3TyZDT/mZEYxyNl1xDs0pxljct9QM6Apz4n5zpIk Cvgi9CSFx/9kay9fyDd+p4LCTrEi/edq6V0RVBNuYz6NqpOAdTp4lvsF8bblcuqZ3dmW 9hl4xpFRKK3iKVqu2atjI6DgusReRyfG5jtu+UQWTkcWqZApMSxCr45RQC0kk/hKEW6b qX6/cU988CSSkhaBVwwljnQ39Lulmw/7IxwM5JIm6Mbg4vN+iw+ZMDt4/WlVxmi2hk7S /uDQ== 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 b5-v6si6473669pgc.150.2018.04.30.11.40.00; Mon, 30 Apr 2018 11:40:18 -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 S1754815AbeD3SjB (ORCPT + 99 others); Mon, 30 Apr 2018 14:39:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41717 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754672AbeD3Si6 (ORCPT ); Mon, 30 Apr 2018 14:38:58 -0400 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2E71E30001DB; Mon, 30 Apr 2018 18:38:58 +0000 (UTC) Received: from w520.home (ovpn-116-103.phx2.redhat.com [10.3.116.103]) by smtp.corp.redhat.com (Postfix) with ESMTP id B9FD9314F9AE; Mon, 30 Apr 2018 18:38:57 +0000 (UTC) Date: Mon, 30 Apr 2018 12:38:57 -0600 From: Alex Williamson To: "dongbo (E)" Cc: , , , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] VFIO: Fix Documentation Message-ID: <20180430123857.006a0697@w520.home> In-Reply-To: <36f5940b-cac5-9a4a-86cb-7ad9766d5d62@huawei.com> References: <1524218521-61496-1-git-send-email-zhangshaokun@hisilicon.com> <36f5940b-cac5-9a4a-86cb-7ad9766d5d62@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.24 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.41]); Mon, 30 Apr 2018 18:38:58 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 20 Apr 2018 18:07:27 +0800 "dongbo (E)" wrote: > From: Dong Bo > > Signed-off-by: Dong Bo > --- Hi Dong Bo, The patch is corrupted, please resend and also include a commit log, something as simple as "Update vfio_add_group_dev description to match the current API" would be fine. Thanks, Alex > 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:: > -- 1.9.1 > > > . > >