From 20acfd68e7dba76ecbe005ce8d01e4121213dec7 Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Mon, 18 Jul 2011 16:15:00 +0000 Subject: [PATCH] --- yaml --- r: 263026 b: refs/heads/master c: ed737c1882c652f0b5a888df59895b5dc2d10cd7 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 0aef3c1d3db1..e38fa8bfedba 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: e4439236ef5ac8e51ce97d03df8ef3e6dc5c6d51 +refs/heads/master: ed737c1882c652f0b5a888df59895b5dc2d10cd7 diff --git a/trunk/Documentation/PCI/MSI-HOWTO.txt b/trunk/Documentation/PCI/MSI-HOWTO.txt index 515396a3d7e3..c504f12bcc61 100644 --- a/trunk/Documentation/PCI/MSI-HOWTO.txt +++ b/trunk/Documentation/PCI/MSI-HOWTO.txt @@ -190,7 +190,7 @@ during the initialization phase. 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 a driver asks for. +exact number that a driver asks for. A request loop to achieve that might look like: