Re: [PATCH v4 1/2] KVM: remove NULL return path for vcpu ids >= KVM_MAX_VCPUS

Quoting Greg Kurz : Commit c896939f7cff ("KVM: use heuristic for fast VCPU lookup by id") added a return path that prevents vcpu ids to exceed KVM_MAX_VCPUS. This is a problem for powerpc where vcpu ids can grow up to 8*KVM_MAX_VCPUS. This patch simply reverses the logic so that we only try fa

[PATCH] m68k: improve m68knommu MAINTAINERS entry

-m68k.org L: uclinux-...@uclinux.org (subscribers-only) +T: git git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git S: Maintained +F: arch/m68k/coldfire/ F: arch/m68k/*/*_no.* F: arch/m68k/include/asm/*_no.* -- 1.9.1 -- To unsubscribe from this list: send

[PATCH] romfs: fix nommu map length to keep inside filesystem

From: Greg Ungerer Checks introduced in commit 4991e7251 ("romfs: do not use mtd->get_unmapped_area directly") re-introduce problems fixed in the earlier commit 2b4b2482e ("romfs: fix romfs_get_unmapped_area() argument check"). If a flat binary app is located at the end of a romfs, its page alig

[PATCH] m68k: select CONFIG_GENERIC_ATOMIC64 for all m68k CPU types

From: Greg Ungerer There is no specific atomic64 support code for any m68k CPUs, so we should select CONFIG_GENERIC_ATOMC64 for all. Remove the existing per CPU selection of this and select it for all m68k. Signed-off-by: Greg Ungerer --- arch/m68k/Kconfig |1 + arch/m68k/Kconfig.cpu |