[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220704023649.3913-1-liubo03@inspur.com>
Date: Sun, 3 Jul 2022 22:36:49 -0400
From: Bo Liu <liubo03@...pur.com>
To: <alex.williamson@...hat.com>, <cohuck@...hat.com>
CC: <kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Bo Liu <liubo03@...pur.com>
Subject: [PATCH] vfio/pci: fix the wrong word
This patch fixes a wrong word in comment.
Signed-off-by: Bo Liu <liubo03@...pur.com>
---
drivers/vfio/pci/vfio_pci_config.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vfio/pci/vfio_pci_config.c b/drivers/vfio/pci/vfio_pci_config.c
index 9343f597182d..97e5ade6efb3 100644
--- a/drivers/vfio/pci/vfio_pci_config.c
+++ b/drivers/vfio/pci/vfio_pci_config.c
@@ -1728,7 +1728,7 @@ int vfio_config_init(struct vfio_pci_core_device *vdev)
/*
* Config space, caps and ecaps are all dword aligned, so we could
* use one byte per dword to record the type. However, there are
- * no requiremenst on the length of a capability, so the gap between
+ * no requirements on the length of a capability, so the gap between
* capabilities needs byte granularity.
*/
map = kmalloc(pdev->cfg_size, GFP_KERNEL);
--
2.27.0
Powered by blists - more mailing lists