Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 412160 Details for
Bug 560738
sys-fs/aufs4 USE="pax_kernel kernel-patch" Fails Patch
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
aufs4-standalone-base-mmap-combined.patch.out
aufs4-standalone-base-mmap-combined.patch.out (text/plain), 44.29 KB, created by
karl
on 2015-09-18 02:12:29 UTC
(
hide
)
Description:
aufs4-standalone-base-mmap-combined.patch.out
Filename:
MIME Type:
Creator:
karl
Created:
2015-09-18 02:12:29 UTC
Size:
44.29 KB
patch
obsolete
>***** aufs4-standalone-base-mmap-combined.patch ***** >PWD: /usr/src/linux >PATCH TOOL: patch -> /usr/bin/patch >VERSION INFO: >GNU patch 2.7.1 >Copyright (C) 2003, 2009-2012 Free Software Foundation, Inc. >Copyright (C) 1988 Larry Wall > >License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. >This is free software: you are free to change and redistribute it. >There is NO WARRANTY, to the extent permitted by law. > >Written by Larry Wall and Paul Eggert > >===================================================== > >PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < '/var/tmp/portage/sys-fs/aufs4-0_pre20150629/temp/aufs4-standalone/aufs4-standalone-base-mmap-combined.patch' > >===================================================== >can't find file to patch at input line 4 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/MAINTAINERS >|+++ b/MAINTAINERS >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 27 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/drivers/block/loop.c >|+++ b/drivers/block/loop.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 55 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/dcache.c >|+++ b/fs/dcache.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 75 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/read_write.c >|+++ b/fs/read_write.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 109 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/splice.c >|+++ b/fs/splice.c >-------------------------- >No file to patch. Skipping patch. >3 out of 3 hunks ignored >can't find file to patch at input line 149 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/file.h >|+++ b/include/linux/file.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 160 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/fs.h >|+++ b/include/linux/fs.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 176 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/splice.h >|+++ b/include/linux/splice.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 190 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/file_table.c >|+++ b/fs/file_table.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 209 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/inode.c >|+++ b/fs/inode.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 220 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/namespace.c >|+++ b/fs/namespace.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 239 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/group.c >|+++ b/fs/notify/group.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 274 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/mark.c >|+++ b/fs/notify/mark.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 309 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/open.c >|+++ b/fs/open.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 328 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/xattr.c >|+++ b/fs/xattr.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 339 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/commoncap.c >|+++ b/security/commoncap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 354 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/device_cgroup.c >|+++ b/security/device_cgroup.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 373 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/security.c >|+++ b/security/security.c >-------------------------- >No file to patch. Skipping patch. >10 out of 10 hunks ignored >can't find file to patch at input line 457 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/buffer.c >|+++ b/fs/buffer.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 470 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/base.c >|+++ b/fs/proc/base.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 483 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/nommu.c >|+++ b/fs/proc/nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 499 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_mmu.c >|+++ b/fs/proc/task_mmu.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 524 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_nommu.c >|+++ b/fs/proc/task_nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 540 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm.h >|+++ b/include/linux/mm.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 573 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm_types.h >|+++ b/include/linux/mm_types.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 593 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/kernel/fork.c >|+++ b/kernel/fork.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 606 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/Makefile >|+++ b/mm/Makefile >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 619 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/filemap.c >|+++ b/mm/filemap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 632 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/madvise.c >|+++ b/mm/madvise.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 651 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/memory.c >|+++ b/mm/memory.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 664 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/mmap.c >|+++ b/mm/mmap.c >-------------------------- >No file to patch. Skipping patch. >8 out of 8 hunks ignored >can't find file to patch at input line 744 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/msync.c >|+++ b/mm/msync.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 761 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/nommu.c >|+++ b/mm/nommu.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >checking file b/mm/prfile.c > >patch program exited with status 1 >===================================================== > >PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < '/var/tmp/portage/sys-fs/aufs4-0_pre20150629/temp/aufs4-standalone/aufs4-standalone-base-mmap-combined.patch' > >===================================================== >checking file MAINTAINERS >checking file drivers/block/loop.c >Hunk #1 succeeded at 538 (offset -2 lines). >checking file fs/dcache.c >Hunk #1 succeeded at 1167 (offset 3 lines). >Hunk #2 succeeded at 1272 (offset 3 lines). >checking file fs/read_write.c >checking file fs/splice.c >checking file include/linux/file.h >checking file include/linux/fs.h >Hunk #1 succeeded at 1650 (offset 1 line). >checking file include/linux/splice.h >checking file fs/file_table.c >checking file fs/inode.c >checking file fs/namespace.c >Hunk #2 succeeded at 1799 (offset 30 lines). >checking file fs/notify/group.c >checking file fs/notify/mark.c >Hunk #4 succeeded at 478 (offset 20 lines). >checking file fs/open.c >Hunk #1 succeeded at 64 (offset 2 lines). >Hunk #2 succeeded at 714 (offset 37 lines). >checking file fs/xattr.c >checking file security/commoncap.c >Hunk #1 succeeded at 1004 (offset 29 lines). >checking file security/device_cgroup.c >checking file security/security.c >Hunk #1 succeeded at 425 (offset -5 lines). >Hunk #2 succeeded at 442 (offset -5 lines). >Hunk #3 succeeded at 451 (offset -5 lines). >Hunk #4 succeeded at 479 (offset -5 lines). >Hunk #5 succeeded at 487 (offset -5 lines). >Hunk #6 succeeded at 495 (offset -5 lines). >Hunk #7 succeeded at 581 (offset -5 lines). >Hunk #8 succeeded at 596 (offset -5 lines). >Hunk #9 succeeded at 719 (offset -5 lines). >Hunk #10 succeeded at 779 (offset -5 lines). >checking file fs/buffer.c >checking file fs/proc/base.c >Hunk #1 succeeded at 1859 (offset 115 lines). >checking file fs/proc/nommu.c >checking file fs/proc/task_mmu.c >Hunk #1 succeeded at 303 (offset 24 lines). >Hunk #2 succeeded at 1530 (offset 48 lines). >checking file fs/proc/task_nommu.c >checking file include/linux/mm.h >Hunk #1 FAILED at 1172. >1 out of 1 hunk FAILED >checking file include/linux/mm_types.h >Hunk #1 succeeded at 232 (offset -9 lines). >Hunk #2 succeeded at 297 (offset -9 lines). >checking file kernel/fork.c >Hunk #1 FAILED at 456. >1 out of 1 hunk FAILED >checking file mm/Makefile >checking file mm/filemap.c >checking file mm/madvise.c >Hunk #1 succeeded at 347 (offset 27 lines). >checking file mm/memory.c >Hunk #1 succeeded at 2060 (offset 26 lines). >checking file mm/mmap.c >Hunk #1 succeeded at 296 (offset 22 lines). >Hunk #2 succeeded at 915 (offset 29 lines). >Hunk #3 succeeded at 1841 (offset 170 lines). >Hunk #4 succeeded at 2879 (offset 406 lines). >Hunk #5 FAILED at 2492. >Hunk #6 succeeded at 3118 (offset 483 lines). >Hunk #7 succeeded at 3166 (offset 488 lines). >Hunk #8 succeeded at 3467 (offset 519 lines). >1 out of 8 hunks FAILED >checking file mm/msync.c >checking file mm/nommu.c >Hunk #1 succeeded at 692 (offset -1 lines). >Hunk #2 succeeded at 857 (offset -1 lines). >Hunk #3 succeeded at 1388 (offset -10 lines). >Hunk #4 succeeded at 1464 (offset -10 lines). >checking file mm/prfile.c > >patch program exited with status 1 >===================================================== > >PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < '/var/tmp/portage/sys-fs/aufs4-0_pre20150629/temp/aufs4-standalone/aufs4-standalone-base-mmap-combined.patch' > >===================================================== >can't find file to patch at input line 4 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/MAINTAINERS >|+++ b/MAINTAINERS >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 27 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/drivers/block/loop.c >|+++ b/drivers/block/loop.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 55 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/dcache.c >|+++ b/fs/dcache.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 75 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/read_write.c >|+++ b/fs/read_write.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 109 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/splice.c >|+++ b/fs/splice.c >-------------------------- >No file to patch. Skipping patch. >3 out of 3 hunks ignored >can't find file to patch at input line 149 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/file.h >|+++ b/include/linux/file.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 160 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/fs.h >|+++ b/include/linux/fs.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 176 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/splice.h >|+++ b/include/linux/splice.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 190 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/file_table.c >|+++ b/fs/file_table.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 209 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/inode.c >|+++ b/fs/inode.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 220 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/namespace.c >|+++ b/fs/namespace.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 239 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/group.c >|+++ b/fs/notify/group.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 274 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/mark.c >|+++ b/fs/notify/mark.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 309 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/open.c >|+++ b/fs/open.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 328 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/xattr.c >|+++ b/fs/xattr.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 339 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/commoncap.c >|+++ b/security/commoncap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 354 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/device_cgroup.c >|+++ b/security/device_cgroup.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 373 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/security.c >|+++ b/security/security.c >-------------------------- >No file to patch. Skipping patch. >10 out of 10 hunks ignored >can't find file to patch at input line 457 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/buffer.c >|+++ b/fs/buffer.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 470 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/base.c >|+++ b/fs/proc/base.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 483 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/nommu.c >|+++ b/fs/proc/nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 499 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_mmu.c >|+++ b/fs/proc/task_mmu.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 524 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_nommu.c >|+++ b/fs/proc/task_nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 540 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm.h >|+++ b/include/linux/mm.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 573 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm_types.h >|+++ b/include/linux/mm_types.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 593 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/kernel/fork.c >|+++ b/kernel/fork.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >checking file Makefile >Hunk #1 FAILED at 21. >1 out of 1 hunk FAILED >can't find file to patch at input line 619 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/filemap.c >|+++ b/mm/filemap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 632 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/madvise.c >|+++ b/mm/madvise.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 651 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/memory.c >|+++ b/mm/memory.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 664 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/mmap.c >|+++ b/mm/mmap.c >-------------------------- >No file to patch. Skipping patch. >8 out of 8 hunks ignored >can't find file to patch at input line 744 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/msync.c >|+++ b/mm/msync.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 761 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/nommu.c >|+++ b/mm/nommu.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >checking file prfile.c > >patch program exited with status 1 >===================================================== > >PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < '/var/tmp/portage/sys-fs/aufs4-0_pre20150629/temp/aufs4-standalone/aufs4-standalone-base-mmap-combined.patch' > >===================================================== >can't find file to patch at input line 4 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/MAINTAINERS >|+++ b/MAINTAINERS >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 27 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/drivers/block/loop.c >|+++ b/drivers/block/loop.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 55 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/dcache.c >|+++ b/fs/dcache.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 75 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/read_write.c >|+++ b/fs/read_write.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 109 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/splice.c >|+++ b/fs/splice.c >-------------------------- >No file to patch. Skipping patch. >3 out of 3 hunks ignored >can't find file to patch at input line 149 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/file.h >|+++ b/include/linux/file.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 160 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/fs.h >|+++ b/include/linux/fs.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 176 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/splice.h >|+++ b/include/linux/splice.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 190 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/file_table.c >|+++ b/fs/file_table.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 209 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/inode.c >|+++ b/fs/inode.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 220 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/namespace.c >|+++ b/fs/namespace.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 239 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/group.c >|+++ b/fs/notify/group.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 274 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/mark.c >|+++ b/fs/notify/mark.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 309 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/open.c >|+++ b/fs/open.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 328 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/xattr.c >|+++ b/fs/xattr.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 339 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/commoncap.c >|+++ b/security/commoncap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 354 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/device_cgroup.c >|+++ b/security/device_cgroup.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 373 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/security.c >|+++ b/security/security.c >-------------------------- >No file to patch. Skipping patch. >10 out of 10 hunks ignored >can't find file to patch at input line 457 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/buffer.c >|+++ b/fs/buffer.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 470 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/base.c >|+++ b/fs/proc/base.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 483 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/nommu.c >|+++ b/fs/proc/nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 499 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_mmu.c >|+++ b/fs/proc/task_mmu.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 524 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_nommu.c >|+++ b/fs/proc/task_nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 540 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm.h >|+++ b/include/linux/mm.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 573 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm_types.h >|+++ b/include/linux/mm_types.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 593 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/kernel/fork.c >|+++ b/kernel/fork.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 606 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/Makefile >|+++ b/mm/Makefile >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 619 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/filemap.c >|+++ b/mm/filemap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 632 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/madvise.c >|+++ b/mm/madvise.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 651 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/memory.c >|+++ b/mm/memory.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 664 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/mmap.c >|+++ b/mm/mmap.c >-------------------------- >No file to patch. Skipping patch. >8 out of 8 hunks ignored >can't find file to patch at input line 744 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/msync.c >|+++ b/mm/msync.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 761 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/nommu.c >|+++ b/mm/nommu.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 805 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- /dev/null >|+++ b/mm/prfile.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored > >patch program exited with status 1 >===================================================== > >PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < '/var/tmp/portage/sys-fs/aufs4-0_pre20150629/temp/aufs4-standalone/aufs4-standalone-base-mmap-combined.patch' > >===================================================== >can't find file to patch at input line 4 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/MAINTAINERS >|+++ b/MAINTAINERS >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 27 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/drivers/block/loop.c >|+++ b/drivers/block/loop.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 55 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/dcache.c >|+++ b/fs/dcache.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 75 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/read_write.c >|+++ b/fs/read_write.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 109 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- b/fs/splice.c >|+++ b/fs/splice.c >-------------------------- >No file to patch. Skipping patch. >3 out of 3 hunks ignored >can't find file to patch at input line 149 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/file.h >|+++ b/include/linux/file.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 160 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/fs.h >|+++ b/include/linux/fs.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 176 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/include/linux/splice.h >|+++ b/include/linux/splice.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 190 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/file_table.c >|+++ b/fs/file_table.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 209 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/inode.c >|+++ b/fs/inode.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 220 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/namespace.c >|+++ b/fs/namespace.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 239 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/group.c >|+++ b/fs/notify/group.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 274 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/notify/mark.c >|+++ b/fs/notify/mark.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 309 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/open.c >|+++ b/fs/open.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 328 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/fs/xattr.c >|+++ b/fs/xattr.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 339 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/commoncap.c >|+++ b/security/commoncap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 354 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/device_cgroup.c >|+++ b/security/device_cgroup.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 373 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|unchanged: >|--- a/security/security.c >|+++ b/security/security.c >-------------------------- >No file to patch. Skipping patch. >10 out of 10 hunks ignored >can't find file to patch at input line 457 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/buffer.c >|+++ b/fs/buffer.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 470 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/base.c >|+++ b/fs/proc/base.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 483 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/nommu.c >|+++ b/fs/proc/nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 499 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_mmu.c >|+++ b/fs/proc/task_mmu.c >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 524 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/fs/proc/task_nommu.c >|+++ b/fs/proc/task_nommu.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 540 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm.h >|+++ b/include/linux/mm.h >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 573 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/include/linux/mm_types.h >|+++ b/include/linux/mm_types.h >-------------------------- >No file to patch. Skipping patch. >2 out of 2 hunks ignored >can't find file to patch at input line 593 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/kernel/fork.c >|+++ b/kernel/fork.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 606 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/Makefile >|+++ b/mm/Makefile >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 619 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/filemap.c >|+++ b/mm/filemap.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 632 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/madvise.c >|+++ b/mm/madvise.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 651 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/memory.c >|+++ b/mm/memory.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 664 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/mmap.c >|+++ b/mm/mmap.c >-------------------------- >No file to patch. Skipping patch. >8 out of 8 hunks ignored >can't find file to patch at input line 744 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/msync.c >|+++ b/mm/msync.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored >can't find file to patch at input line 761 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- a/mm/nommu.c >|+++ b/mm/nommu.c >-------------------------- >No file to patch. Skipping patch. >4 out of 4 hunks ignored >can't find file to patch at input line 805 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >|only in patch2: >|unchanged: >|--- /dev/null >|+++ b/mm/prfile.c >-------------------------- >No file to patch. Skipping patch. >1 out of 1 hunk ignored > >patch program exited with status 1
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 560738
: 412160 |
412702