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

Documentation: Fix power typos

Fix typos.

Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250813200526.290420-8-helgaas@kernel.org

authored by

Bjorn Helgaas and committed by
Jonathan Corbet
3dae66ae e855d7e5

+3 -3
+2 -2
Documentation/power/pci.rst
··· 472 472 The pci_pm_suspend_noirq() routine is executed after suspend_device_irqs() has 473 473 been called, which means that the device driver's interrupt handler won't be 474 474 invoked while this routine is running. It first checks if the device's driver 475 - implements legacy PCI suspends routines (Section 3), in which case the legacy 475 + implements legacy PCI suspend routines (Section 3), in which case the legacy 476 476 late suspend routine is called and its result is returned (the standard 477 477 configuration registers of the device are saved if the driver's callback hasn't 478 478 done that). Second, if the device driver's struct dev_pm_ops object is not ··· 544 544 The resume phase is carried out asynchronously for PCI devices, like the 545 545 suspend phase described above, which means that if two PCI devices don't depend 546 546 on each other in a known way, the pci_pm_resume() routine may be executed for 547 - the both of them in parallel. 547 + both of them in parallel. 548 548 549 549 The pci_pm_complete() routine only executes the device driver's pm->complete() 550 550 callback, if defined.
+1 -1
Documentation/power/suspend-and-cpuhotplug.rst
··· 13 13 14 14 Well, a picture is worth a thousand words... So ASCII art follows :-) 15 15 16 - [This depicts the current design in the kernel, and focusses only on the 16 + [This depicts the current design in the kernel, and focuses only on the 17 17 interactions involving the freezer and CPU hotplug and also tries to explain 18 18 the locking involved. It outlines the notifications involved as well. 19 19 But please note that here, only the call paths are illustrated, with the aim