mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>, kvm <kvm@vger.kernel.org>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] vfio/pci: fix a couple of spelling mistakes
Date: Fri, 26 Mar 2021 10:18:59 +0100	[thread overview]
Message-ID: <f2d898cb-77ca-5057-1aff-6c20b0861fa3@redhat.com> (raw)
In-Reply-To: <20210326083528.1329-4-thunder.leizhen@huawei.com>



On 3/26/21 9:35 AM, Zhen Lei wrote:
> There are several spelling mistakes, as follows:
> permision ==> permission
> thru ==> through
> presense ==> presence
> 
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>

Eric
> ---
>  drivers/vfio/pci/vfio_pci.c         | 2 +-
>  drivers/vfio/pci/vfio_pci_config.c  | 2 +-
>  drivers/vfio/pci/vfio_pci_nvlink2.c | 4 ++--
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> index 65e7e6b44578c29..d2ab8b5bc8a86fe 100644
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -2409,7 +2409,7 @@ static int __init vfio_pci_init(void)
>  {
>  	int ret;
>  
> -	/* Allocate shared config space permision data used by all devices */
> +	/* Allocate shared config space permission data used by all devices */
>  	ret = vfio_pci_init_perm_bits();
>  	if (ret)
>  		return ret;
> diff --git a/drivers/vfio/pci/vfio_pci_config.c b/drivers/vfio/pci/vfio_pci_config.c
> index a402adee8a21558..d57f037f65b85d4 100644
> --- a/drivers/vfio/pci/vfio_pci_config.c
> +++ b/drivers/vfio/pci/vfio_pci_config.c
> @@ -101,7 +101,7 @@
>  /*
>   * Read/Write Permission Bits - one bit for each bit in capability
>   * Any field can be read if it exists, but what is read depends on
> - * whether the field is 'virtualized', or just pass thru to the
> + * whether the field is 'virtualized', or just pass through to the
>   * hardware.  Any virtualized field is also virtualized for writes.
>   * Writes are only permitted if they have a 1 bit here.
>   */
> diff --git a/drivers/vfio/pci/vfio_pci_nvlink2.c b/drivers/vfio/pci/vfio_pci_nvlink2.c
> index 9adcf6a8f888575..f276624fec79f68 100644
> --- a/drivers/vfio/pci/vfio_pci_nvlink2.c
> +++ b/drivers/vfio/pci/vfio_pci_nvlink2.c
> @@ -219,7 +219,7 @@ int vfio_pci_nvdia_v100_nvlink2_init(struct vfio_pci_device *vdev)
>  	unsigned long events = VFIO_GROUP_NOTIFY_SET_KVM;
>  
>  	/*
> -	 * PCI config space does not tell us about NVLink presense but
> +	 * PCI config space does not tell us about NVLink presence but
>  	 * platform does, use this.
>  	 */
>  	npu_dev = pnv_pci_get_npu_dev(vdev->pdev, 0);
> @@ -402,7 +402,7 @@ int vfio_pci_ibm_npu2_init(struct vfio_pci_device *vdev)
>  	u32 link_speed = 0xff;
>  
>  	/*
> -	 * PCI config space does not tell us about NVLink presense but
> +	 * PCI config space does not tell us about NVLink presence but
>  	 * platform does, use this.
>  	 */
>  	if (!pnv_pci_get_gpu_dev(vdev->pdev))
> 


  reply	other threads:[~2021-03-26  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  8:35 [PATCH 0/4] vfio: fix a couple of spelling mistakes detected by codespell tool Zhen Lei
2021-03-26  8:35 ` [PATCH 1/4] vfio/type1: fix a couple of spelling mistakes Zhen Lei
2021-03-26  9:20   ` Auger Eric
2021-03-26  8:35 ` [PATCH 2/4] vfio/mdev: Fix spelling mistake "interal" -> "internal" Zhen Lei
2021-03-26  9:19   ` Auger Eric
2021-03-26  8:35 ` [PATCH 3/4] vfio/pci: fix a couple of spelling mistakes Zhen Lei
2021-03-26  9:18   ` Auger Eric [this message]
2021-03-26  8:35 ` [PATCH 4/4] vfio/platform: Fix spelling mistake "registe" -> "register" Zhen Lei
2021-03-26  9:17   ` Auger Eric
2021-04-06 19:37 ` [PATCH 0/4] vfio: fix a couple of spelling mistakes detected by codespell tool Alex Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f2d898cb-77ca-5057-1aff-6c20b0861fa3@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder.leizhen@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®