summaryrefslogtreecommitdiffstats
path: root/Kbuild
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-01-15 19:54:39 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2017-01-15 19:54:39 +0100
commit255e6140fa76ec9d0e24f201427e7e9a9573f681 (patch)
tree242eda3c33f43faff66591f1e125169bb9a602bb /Kbuild
parentMerge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/vir... (diff)
parentefi/x86: Prune invalid memory map entries and fix boot regression (diff)
downloadlinux-255e6140fa76ec9d0e24f201427e7e9a9573f681.tar.xz
linux-255e6140fa76ec9d0e24f201427e7e9a9573f681.zip
Merge branch 'efi-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull EFI fixes from Ingo Molnar: "A number of regression fixes: - Fix a boot hang on machines that have somewhat unusual memory map entries of phys_addr=0x0 num_pages=0, which broke due to a recent commit. This commit got cherry-picked from the v4.11 queue because the bug is affecting real machines. - Fix a boot hang also reported by KASAN, caused by incorrect init ordering introduced by a recent optimization. - Fix a recent robustification fix to allocate_new_fdt_and_exit_boot() that introduced an invalid assumption. Neither bugs were seen in the wild AFAIK" * 'efi-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: efi/x86: Prune invalid memory map entries and fix boot regression x86/efi: Don't allocate memmap through memblock after mm_init() efi/libstub/arm*: Pass latest memory map to the kernel
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions