diff options
| author | Bjorn Helgaas <bhelgaas@google.com> | 2025-03-07 17:17:15 -0600 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2025-03-08 15:08:45 -0600 |
| commit | f4e026f454d7bb6aa84901a37641132961054735 (patch) | |
| tree | e6686eae2f068482c869a396664f14deeec6acc9 /drivers/pci/of.c | |
| parent | 86c2345aff3f5b48b53a73a15ffe6e0930e4170f (diff) | |
PCI: Fix typos
Fix typos and whitespace errors.
Link: https://lore.kernel.org/r/20250307231715.438518-1-helgaas@kernel.org
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'drivers/pci/of.c')
| -rw-r--r-- | drivers/pci/of.c | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/drivers/pci/of.c b/drivers/pci/of.c index 7a806f5c0d20..0e4f9119f5f2 100644 --- a/drivers/pci/of.c +++ b/drivers/pci/of.c @@ -455,9 +455,9 @@ failed: * @out_irq: structure of_phandle_args filled by this function * * This function resolves the PCI interrupt for a given PCI device. If a - * device-node exists for a given pci_dev, it will use normal OF tree + * device node exists for a given pci_dev, it will use normal OF tree * walking. If not, it will implement standard swizzling and walk up the - * PCI tree until an device-node is found, at which point it will finish + * PCI tree until a device node is found, at which point it will finish * resolving using the OF tree walking. */ static int of_irq_parse_pci(const struct pci_dev *pdev, struct of_phandle_args *out_irq) @@ -517,13 +517,16 @@ static int of_irq_parse_pci(const struct pci_dev *pdev, struct of_phandle_args * } /* - * Ok, we have found a parent with a device-node, hand over to + * Ok, we have found a parent with a device node, hand over to * the OF parsing code. + * * We build a unit address from the linux device to be used for * resolution. Note that we use the linux bus number which may * not match your firmware bus numbering. + * * Fortunately, in most cases, interrupt-map-mask doesn't * include the bus number as part of the matching. + * * You should still be careful about that though if you intend * to rely on this function (you ship a firmware that doesn't * create device nodes for all PCI devices). |