The patch titled
i386: fix GDT's number of quadwords in comment
has been added to the -mm tree. Its filename is
i386-fix-gdts-number-of-quadwords-in.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: i386: fix GDT's number of quadwords in comment
From: Ahmed S. Darwish <darwish.07@xxxxxxxxx>
Fix comments to represent the true number of quadwords in GDT.
Signed-off-by: Ahmed S. Darwish <darwish.07@xxxxxxxxx>
Acked-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/i386/kernel/head.S | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/i386/kernel/head.S~i386-fix-gdts-number-of-quadwords-in arch/i386/kernel/head.S
--- a/arch/i386/kernel/head.S~i386-fix-gdts-number-of-quadwords-in
+++ a/arch/i386/kernel/head.S
@@ -612,7 +612,7 @@ ENTRY(boot_gdt_table)
.quad 0x00cf92000000ffff /* kernel 4GB data at 0x00000000 */
/*
- * The Global Descriptor Table contains 28 quadwords, per-CPU.
+ * The Global Descriptor Table contains 32 quadwords, per-CPU.
*/
.align L1_CACHE_BYTES
ENTRY(cpu_gdt_table)
@@ -639,7 +639,7 @@ ENTRY(cpu_gdt_table)
/*
* Segments used for calling PnP BIOS have byte granularity.
- * They code segments and data segments have fixed 64k limits,
+ * The code segments and data segments have fixed 64k limits,
* the transfer segment sizes are set at run time.
*/
.quad 0x00409a000000ffff /* 0x90 32-bit code */
_
Patches currently in -mm which might be from darwish.07@xxxxxxxxx are
git-avr32.patch
git-drm.patch
git-kvm.patch
s390-kmalloc-kzalloc-casting-cleanups.patch
i386-fix-gdts-number-of-quadwords-in.patch
rcutorture-use-array_size-macro-when-appropriate.patch
drivers-mdc-use-array_size-macro-when-appropriate.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
