On Wed, Jun 10, 2015 at 02:58:33AM -0400, St??phane ancelot wrote: > here is an example with linux-3.18.13 and patch 3.18.13-rt10: > 3.18.13-rt10 > > zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run > patching file arch/arm64/kernel/perf_event.c > Hunk #1 succeeded at 461 (offset -6 lines). > patching file arch/sparc/Kconfig > patching file arch/arm64/Kconfig > Hunk #1 succeeded at 61 (offset -7 lines). > patching file include/linux/notifier.h > patching file include/linux/srcu.h > patching file arch/x86/mm/iomap_32.c > Hunk #1 FAILED at 65. > 1 out of 1 hunk FAILED -- saving rejects to file arch/x86/mm/iomap_32.c.rej It appears you are applying the patch to an Android or other third-party derivative of Linux, instead of Linux proper, or that either the kernel or the patch you have fetched is corrupt. Try re-fetching everything and try again. This sequence works for me: cd mkdir junk cd junk wget -q ftp://ftp.kernel.org/pub/linux/kernel/v3.0/linux-3.18.11.tar.xz wget -q ftp://ftp.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13-rt10.patch.xz tar xf l*xz cd linux*11 unxz <../pat*xz | patch -p1 There are some (annoying) offset errors, but no fuzzies or rejects like you have been seeing. Joe -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
