Docs: MSI-HOWTO: Put the `because' subordinate clause first

Signed-off-by: Michael Witten <mfwitten@gmail.com>
Acked-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
This commit is contained in:
Michael Witten
2011-07-14 21:28:00 +00:00
parent 1d15afcc73
commit 263d8d57b3
+4 -4
View File
@@ -137,8 +137,8 @@ interrupt number and frees the previously allocated message signaled
interrupt(s). The interrupt may subsequently be assigned to another interrupt(s). The interrupt may subsequently be assigned to another
device, so drivers should not cache the value of dev->irq. device, so drivers should not cache the value of dev->irq.
A device driver must always call free_irq() on the interrupt(s) Before calling this function, a device driver must always call free_irq()
for which it has called request_irq() before calling this function. on any interrupt for which it previously called request_irq().
Failure to do so results in a BUG_ON(), leaving the device with Failure to do so results in a BUG_ON(), leaving the device with
MSI enabled and thus leaking its vector. MSI enabled and thus leaking its vector.
@@ -217,8 +217,8 @@ the previously allocated message signaled interrupts. The interrupts may
subsequently be assigned to another device, so drivers should not cache subsequently be assigned to another device, so drivers should not cache
the value of the 'vector' elements over a call to pci_disable_msix(). the value of the 'vector' elements over a call to pci_disable_msix().
A device driver must always call free_irq() on the interrupt(s) Before calling this function, a device driver must always call free_irq()
for which it has called request_irq() before calling this function. on any interrupt for which it previously called request_irq().
Failure to do so results in a BUG_ON(), leaving the device with Failure to do so results in a BUG_ON(), leaving the device with
MSI-X enabled and thus leaking its vector. MSI-X enabled and thus leaking its vector.