Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

vfio/pci: Fix typos in comments

Signed-off-by: Wei Jiangang <weijg.fnst@cn.fujitsu.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>

authored by

Wei Jiangang and committed by
Alex Williamson
8138dabb 3eab887a

+4 -4
+4 -4
drivers/vfio/pci/vfio_pci_config.c
··· 70 70 71 71 /* 72 72 * Lengths of PCIe/PCI-X Extended Config Capabilities 73 - * 0: Removed or masked from the user visible capabilty list 73 + * 0: Removed or masked from the user visible capability list 74 74 * FF: Variable length 75 75 */ 76 76 static const u16 pci_ext_cap_length[PCI_EXT_CAP_ID_MAX + 1] = { ··· 355 355 * ignore whether a read/write exceeds the defined capability 356 356 * structure. We can do this because: 357 357 * - Standard config space is already dword aligned 358 - * - Capabilities are all dword alinged (bits 0:1 of next reserved) 358 + * - Capabilities are all dword aligned (bits 0:1 of next reserved) 359 359 * - Express capabilities defined as dword aligned 360 360 */ 361 361 size = round_up(size, 4); ··· 1516 1516 * space which tracks reads and writes to bits that we emulate for 1517 1517 * the user. Initial values filled from device. 1518 1518 * 1519 - * Using shared stuct perm_bits between all vfio-pci devices saves 1519 + * Using shared struct perm_bits between all vfio-pci devices saves 1520 1520 * us from allocating cfg_size buffers for virt and write for every 1521 1521 * device. We could remove vconfig and allocate individual buffers 1522 - * for each area requring emulated bits, but the array of pointers 1522 + * for each area requiring emulated bits, but the array of pointers 1523 1523 * would be comparable in size (at least for standard config space). 1524 1524 */ 1525 1525 int vfio_config_init(struct vfio_pci_device *vdev)