The patch titled
i386 boot: Add an ELF header to bzImage (fix 99)
has been removed from the -mm tree. Its filename is
i386-boot-add-an-elf-header-to-bzimage-fix-fix-fix-fix.patch
This patch was dropped because it was folded into i386-boot-add-an-elf-header-to-bzimage.patch
------------------------------------------------------
Subject: i386 boot: Add an ELF header to bzImage (fix 99)
From: Vivek Goyal <vgoyal@xxxxxxxxxx>
Ok. I have added the "cld" early in the setup code. I am still retaining
the call to "cld" just before string instruction to be on the safer side.
Singed-off-by: Eric Biederman <ebiederm@xxxxxxxxxxxx>
Signed-off-by: Vivek Goyal <vgoyal@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/i386/boot/setup.S | 1 +
1 files changed, 1 insertion(+)
diff -puN arch/i386/boot/setup.S~i386-boot-add-an-elf-header-to-bzimage-fix-fix-fix-fix arch/i386/boot/setup.S
--- a/arch/i386/boot/setup.S~i386-boot-add-an-elf-header-to-bzimage-fix-fix-fix-fix
+++ a/arch/i386/boot/setup.S
@@ -167,6 +167,7 @@ trampoline: call start_of_setup
# End of setup header #####################################################
start_of_setup:
+ cld # set DF=0
# Bootlin depends on this being done early
movw $0x01500, %ax
movb $0x81, %dl
_
Patches currently in -mm which might be from vgoyal@xxxxxxxxxx are
x86_64-overlapping-program-headers-in-physical-addr-space-fix.patch
i386-distinguish-absolute-symbols.patch
i386-align-data-section-to-4k-boundary.patch
i386-define-__pa_symbol-2.patch
i386-setupc-reserve-kernel-memory-starting-from-_text.patch
i386-config_physical_start-cleanup.patch
make-linux-elfh-safe-to-be-included-in-assembly-files.patch
elf-add-elfosabi_standalone-to-elfh.patch
kallsyms-generate-relocatable-symbols.patch
i386-relocatable-kernel-support.patch
i386-implement-config_physical_align.patch
i386-boot-add-an-elf-header-to-bzimage.patch
i386-boot-add-an-elf-header-to-bzimage-fix-fix-fix-fix.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
