path: root/Documentation/PCI/MSI-HOWTO.txt
diff options
authorMichael Witten <mfwitten@gmail.com>2011-07-15 03:25:44 +0000
committerMichael Witten <mfwitten@gmail.com>2011-08-02 21:34:39 +0000
commite6b85a1f8a56d3c9db0273b7e4aaab802dc07a9b (patch)
tree0ef566d56bba071c08abbf7fb3a2f4f38414364a /Documentation/PCI/MSI-HOWTO.txt
parent952df55b5a30913f4a5536b12ad09dd95c66d83f (diff)
Docs: MSI-HOWTO: Use `unknown ...' rather than `... know about.'
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>
Diffstat (limited to 'Documentation/PCI/MSI-HOWTO.txt')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/PCI/MSI-HOWTO.txt b/Documentation/PCI/MSI-HOWTO.txt
index 257628fdd464..2322a570beb5 100644
--- a/Documentation/PCI/MSI-HOWTO.txt
+++ b/Documentation/PCI/MSI-HOWTO.txt
@@ -316,7 +316,7 @@ Some bridges allow you to enable MSIs by changing some bits in their
PCI configuration space (especially the Hypertransport chipsets such
as the nVidia nForce and Serverworks HT2000). As with host chipsets,
Linux mostly knows about them and automatically enables MSIs if it can.
-If you have a bridge which Linux doesn't yet know about, you can enable
+If you have a bridge unknown to Linux, you can enable
MSIs in configuration space using whatever method you know works, then
enable MSIs on that bridge by doing:

Privacy Policy