patch error output

aufs4-standalone-base-mmap-combined.patch.out (text/plain), 40.71 KB, created by Buggy Bug on 2016-03-23 18:41:21 UTC

***** aufs4-standalone-base-mmap-combined.patch *****
PWD: /usr/src/linux
PATCH TOOL: patch -> /usr/bin/patch
VERSION INFO:
GNU patch 2.7.5
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  --dry-run -f < '/var/tmp/portage/sys-fs/aufs4-0_pre20160223/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/exec.c
|+++ b/fs/exec.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 201
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.
4 out of 4 hunks ignored
can't find file to patch at input line 236
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 255
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 290
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 325
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 344
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 355
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|unchanged:
|--- a/kernel/task_work.c
|+++ b/kernel/task_work.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 363
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 381
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 400
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 484
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 497
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 513
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 538
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 554
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 587
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 607
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 620
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 633
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 646
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 659
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 739
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  --dry-run -f < '/var/tmp/portage/sys-fs/aufs4-0_pre20160223/temp/aufs4-standalone/aufs4-standalone-base-mmap-combined.patch'

=====================================================
checking file MAINTAINERS
checking file drivers/block/loop.c
checking file fs/dcache.c
checking file fs/read_write.c
Hunk #1 succeeded at 516 with fuzz 2 (offset 22 lines).
checking file fs/splice.c
Hunk #2 FAILED at 1123.
1 out of 3 hunks FAILED
checking file include/linux/file.h
checking file include/linux/fs.h
checking file include/linux/splice.h
checking file fs/exec.c
checking file fs/file_table.c
checking file fs/namespace.c
checking file fs/notify/group.c
checking file fs/notify/mark.c
checking file fs/open.c
checking file fs/xattr.c
checking file kernel/task_work.c
checking file security/commoncap.c
Hunk #1 succeeded at 1058 (offset 5 lines).
checking file security/device_cgroup.c
checking file security/security.c
checking file fs/proc/base.c
Hunk #1 succeeded at 1922 (offset 1 line).
checking file fs/proc/nommu.c
checking file fs/proc/task_mmu.c
Hunk #2 succeeded at 1509 (offset 1 line).
checking file fs/proc/task_nommu.c
checking file include/linux/mm.h
checking file include/linux/mm_types.h
checking file kernel/fork.c
checking file mm/Makefile
checking file mm/filemap.c
checking file mm/memory.c
checking file mm/mmap.c
Hunk #2 succeeded at 891 (offset 4 lines).
Hunk #3 succeeded at 1685 (offset 4 lines).
Hunk #4 succeeded at 2483 (offset -5 lines).
Hunk #5 succeeded at 2502 (offset -5 lines).
Hunk #6 succeeded at 2644 (offset -5 lines).
Hunk #7 succeeded at 2711 with fuzz 1 (offset 19 lines).
Hunk #8 succeeded at 2984 (offset 19 lines).
checking file mm/nommu.c
checking file mm/prfile.c

patch program exited with status 1
=====================================================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch  --dry-run -f < '/var/tmp/portage/sys-fs/aufs4-0_pre20160223/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/exec.c
|+++ b/fs/exec.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 201
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.
4 out of 4 hunks ignored
can't find file to patch at input line 236
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 255
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 290
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 325
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 344
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 355
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|unchanged:
|--- a/kernel/task_work.c
|+++ b/kernel/task_work.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 363
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 381
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 400
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 484
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 497
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 513
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 538
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 554
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 587
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 607
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 633
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 646
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 659
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 739
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  --dry-run -f < '/var/tmp/portage/sys-fs/aufs4-0_pre20160223/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/exec.c
|+++ b/fs/exec.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 201
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.
4 out of 4 hunks ignored
can't find file to patch at input line 236
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 255
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 290
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 325
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 344
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 355
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|unchanged:
|--- a/kernel/task_work.c
|+++ b/kernel/task_work.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 363
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 381
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 400
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 484
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 497
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 513
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 538
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 554
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 587
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 607
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 620
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 633
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 646
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 659
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 739
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 783
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  --dry-run -f < '/var/tmp/portage/sys-fs/aufs4-0_pre20160223/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/exec.c
|+++ b/fs/exec.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 201
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.
4 out of 4 hunks ignored
can't find file to patch at input line 236
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 255
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 290
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 325
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 344
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 355
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|unchanged:
|--- a/kernel/task_work.c
|+++ b/kernel/task_work.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 363
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 381
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 400
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 484
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 497
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 513
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 538
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 554
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 587
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 607
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 620
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 633
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 646
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 659
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 739
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 783
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