From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932740AbcHXKKC (ORCPT ); Wed, 24 Aug 2016 06:10:02 -0400 Received: from cn.fujitsu.com ([59.151.112.132]:34883 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751025AbcHXKJ6 (ORCPT ); Wed, 24 Aug 2016 06:09:58 -0400 X-IronPort-AV: E=Sophos;i="5.22,518,1449504000"; d="scan'208";a="10235261" From: "Wei, Jiangang" To: "linux-kernel@vger.kernel.org" CC: "dan.carpenter@oracle.com" , "alex.williamson@redhat.com" , "mark.d.rustad@intel.com" , "aik@ozlabs.ru" Subject: Re: [PATCH] vfio/pci: Fix typos in comments Thread-Topic: [PATCH] vfio/pci: Fix typos in comments Thread-Index: AQHR+FHduA4SaOuzU0GD7XUZewegdKBXaEaA Date: Wed, 24 Aug 2016 10:09:01 +0000 Message-ID: <1472033331.7011.27.camel@localhost> References: <1471415825-9231-1-git-send-email-weijg.fnst@cn.fujitsu.com> In-Reply-To: <1471415825-9231-1-git-send-email-weijg.fnst@cn.fujitsu.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.167.226.50] Content-Type: text/plain; charset="utf-8" Content-ID: <65EA5ECC4813234DB6EE38BE0F1F55F2@fujitsu.local> MIME-Version: 1.0 X-yoursite-MailScanner-ID: 9C998430CD06.A83A8 X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: weijg.fnst@cn.fujitsu.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u7OAABUg029456 ping... On Wed, 2016-08-17 at 14:37 +0800, Wei Jiangang wrote: > Signed-off-by: Wei Jiangang > --- > drivers/vfio/pci/vfio_pci_config.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/vfio/pci/vfio_pci_config.c b/drivers/vfio/pci/vfio_pci_config.c > index 688691d9058d..c4f235452d81 100644 > --- a/drivers/vfio/pci/vfio_pci_config.c > +++ b/drivers/vfio/pci/vfio_pci_config.c > @@ -70,7 +70,7 @@ static const u8 pci_cap_length[PCI_CAP_ID_MAX + 1] = { > > /* > * Lengths of PCIe/PCI-X Extended Config Capabilities > - * 0: Removed or masked from the user visible capabilty list > + * 0: Removed or masked from the user visible capability list > * FF: Variable length > */ > static const u16 pci_ext_cap_length[PCI_EXT_CAP_ID_MAX + 1] = { > @@ -355,7 +355,7 @@ static int alloc_perm_bits(struct perm_bits *perm, int size) > * ignore whether a read/write exceeds the defined capability > * structure. We can do this because: > * - Standard config space is already dword aligned > - * - Capabilities are all dword alinged (bits 0:1 of next reserved) > + * - Capabilities are all dword aligned (bits 0:1 of next reserved) > * - Express capabilities defined as dword aligned > */ > size = round_up(size, 4); > @@ -1516,10 +1516,10 @@ static int vfio_ecap_init(struct vfio_pci_device *vdev) > * space which tracks reads and writes to bits that we emulate for > * the user. Initial values filled from device. > * > - * Using shared stuct perm_bits between all vfio-pci devices saves > + * Using shared struct perm_bits between all vfio-pci devices saves > * us from allocating cfg_size buffers for virt and write for every > * device. We could remove vconfig and allocate individual buffers > - * for each area requring emulated bits, but the array of pointers > + * for each area requiring emulated bits, but the array of pointers > * would be comparable in size (at least for standard config space). > */ > int vfio_config_init(struct vfio_pci_device *vdev)