fix the wording in an x86 patch for .24 and .25 on request from Ingo

diff --git a/review-2.6.24/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch b/review-2.6.24/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch
index 72e769b0f14db151452b10ce42639898d7766f3c..8d700502d34ca103a96799128013e8b749c5b989 100644 (file)
--- a/review-2.6.24/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch
+++ b/review-2.6.24/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch
@@ -10,7 +10,7 @@ From: PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>
 
 commit 9d9ad4b51d2b29b5bbeb4011f5e76f7538119cf9 upstream
 
-This bug was introduced in the 2.6.24 i386/x86_64 tree merge, where
+This bug was introduced in the 2.6.24 lguest tree merge, where
 MSI-X vector allocation will eventually fail.  The cause is the new
 bit array tracking used vectors is not getting cleared properly on
 IRQ destruction on the 32-bit APIC code.

diff --git a/review-2.6.25/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch b/review-2.6.25/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch
index 5cf5e016e1d347d7e06a27e49d8dc8ec56208646..7caf211fb63de415e3ade50e091f10fdc16911aa 100644 (file)
--- a/review-2.6.25/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch
+++ b/review-2.6.25/x86-fix-32-bit-x86-msi-x-allocation-leakage.patch
@@ -10,7 +10,7 @@ From: PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>
 
 commit 9d9ad4b51d2b29b5bbeb4011f5e76f7538119cf9 upstream
 
-This bug was introduced in the 2.6.24 i386/x86_64 tree merge, where
+This bug was introduced in the 2.6.24 lguest merge, where
 MSI-X vector allocation will eventually fail.  The cause is the new
 bit array tracking used vectors is not getting cleared properly on
 IRQ destruction on the 32-bit APIC code.