aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/PCI
diff options
context:
space:
mode:
authorMichael Witten <mfwitten@gmail.com>2011-07-14 23:25:44 -0400
committerMichael Witten <mfwitten@gmail.com>2011-08-02 17:34:39 -0400
commite6b85a1f8a56d3c9db0273b7e4aaab802dc07a9b (patch)
tree0ef566d56bba071c08abbf7fb3a2f4f38414364a /Documentation/PCI
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')
-rw-r--r--Documentation/PCI/MSI-HOWTO.txt2
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
316PCI configuration space (especially the Hypertransport chipsets such 316PCI configuration space (especially the Hypertransport chipsets such
317as the nVidia nForce and Serverworks HT2000). As with host chipsets, 317as the nVidia nForce and Serverworks HT2000). As with host chipsets,
318Linux mostly knows about them and automatically enables MSIs if it can. 318Linux mostly knows about them and automatically enables MSIs if it can.
319If you have a bridge which Linux doesn't yet know about, you can enable 319If you have a bridge unknown to Linux, you can enable
320MSIs in configuration space using whatever method you know works, then 320MSIs in configuration space using whatever method you know works, then
321enable MSIs on that bridge by doing: 321enable MSIs on that bridge by doing:
322 322