From f5f0e275fc9af1ab93a3bd96e6b0642ebb29ebd9 Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Thu, 14 Jul 2011 21:55:05 +0000 Subject: [PATCH] --- yaml --- r: 263028 b: refs/heads/master c: 5a84fc3162e06632ebea42cefe3b964299213d33 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/PCI/MSI-HOWTO.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 8a4a320ca0a8..64fdd8b93432 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 6457d9b350b3f4f2098984eee016c6c994b9c096 +refs/heads/master: 5a84fc3162e06632ebea42cefe3b964299213d33 diff --git a/trunk/Documentation/PCI/MSI-HOWTO.txt b/trunk/Documentation/PCI/MSI-HOWTO.txt index 28d1ceeea655..f533bc2f283c 100644 --- a/trunk/Documentation/PCI/MSI-HOWTO.txt +++ b/trunk/Documentation/PCI/MSI-HOWTO.txt @@ -187,7 +187,7 @@ number once MSI-X is enabled. Device drivers should normally call this function once per device during the initialization phase. -It is ideal if drivers can cope with a variable number of MSI-X interrupts, +It is ideal if drivers can cope with a variable number of MSI-X interrupts; there are many reasons why the platform may not be able to provide the exact number that a driver asks for.