There are several spelling mistakes, as follows:
userpsace ==> userspace
Accouting ==> Accounting
exlude ==> exclude
Signed-off-by: Zhen Lei <[email protected]>
---
drivers/vfio/vfio_iommu_type1.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
index be444407664af74..21cf1d123036c82 100644
--- a/drivers/vfio/vfio_iommu_type1.c
+++ b/drivers/vfio/vfio_iommu_type1.c
@@ -16,7 +16,7 @@
* IOMMU to support the IOMMU API and have few to no restrictions around
* the IOVA range that can be mapped. The Type1 IOMMU is currently
* optimized for relatively static mappings of a userspace process with
- * userpsace pages pinned into memory. We also assume devices and IOMMU
+ * userspace pages pinned into memory. We also assume devices and IOMMU
* domains are PCI based as the IOMMU API is still centered around a
* device/bus interface rather than a group interface.
*/
@@ -871,7 +871,7 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,
/*
* If iommu capable domain exist in the container then all pages are
- * already pinned and accounted. Accouting should be done if there is no
+ * already pinned and accounted. Accounting should be done if there is no
* iommu capable domain in the container.
*/
do_accounting = !IS_IOMMU_CAP_DOMAIN_IN_CONTAINER(iommu);
@@ -2171,7 +2171,7 @@ static int vfio_iommu_resv_exclude(struct list_head *iova,
continue;
/*
* Insert a new node if current node overlaps with the
- * reserve region to exlude that from valid iova range.
+ * reserve region to exclude that from valid iova range.
* Note that, new node is inserted before the current
* node and finally the current node is deleted keeping
* the list updated and sorted.
--
1.8.3
Hi,
On 3/26/21 9:35 AM, Zhen Lei wrote:
> There are several spelling mistakes, as follows:
> userpsace ==> userspace
> Accouting ==> Accounting
> exlude ==> exclude
Reviewed-by: Eric Auger <[email protected]>
Thanks
Eric
>
> Signed-off-by: Zhen Lei <[email protected]>
> ---
> drivers/vfio/vfio_iommu_type1.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index be444407664af74..21cf1d123036c82 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -16,7 +16,7 @@
> * IOMMU to support the IOMMU API and have few to no restrictions around
> * the IOVA range that can be mapped. The Type1 IOMMU is currently
> * optimized for relatively static mappings of a userspace process with
> - * userpsace pages pinned into memory. We also assume devices and IOMMU
> + * userspace pages pinned into memory. We also assume devices and IOMMU
> * domains are PCI based as the IOMMU API is still centered around a
> * device/bus interface rather than a group interface.
> */
> @@ -871,7 +871,7 @@ static int vfio_iommu_type1_pin_pages(void *iommu_data,
>
> /*
> * If iommu capable domain exist in the container then all pages are
> - * already pinned and accounted. Accouting should be done if there is no
> + * already pinned and accounted. Accounting should be done if there is no
> * iommu capable domain in the container.
> */
> do_accounting = !IS_IOMMU_CAP_DOMAIN_IN_CONTAINER(iommu);
> @@ -2171,7 +2171,7 @@ static int vfio_iommu_resv_exclude(struct list_head *iova,
> continue;
> /*
> * Insert a new node if current node overlaps with the
> - * reserve region to exlude that from valid iova range.
> + * reserve region to exclude that from valid iova range.
> * Note that, new node is inserted before the current
> * node and finally the current node is deleted keeping
> * the list updated and sorted.
>