***** parallels-workstation-2.2.2112-2.6.23.patch ***** ======================================================= PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/app-emulation/parallels-workstation/files/parallels-workstation-2.2.2112-2.6.23.patch ======================================================= patching file data/drivers/drv_main/compat/compat_memory.h patching file data/drivers/drv_main/Makefile patching file data/drivers/drv_main/mm/manager.c patching file data/drivers/drv_main/mm/pages.c patching file data/drivers/drv_main/vmmain.h patching file data/drivers/drv_net/linux/prlnet.c Hunk #1 FAILED at 6. 1 out of 22 hunks FAILED -- saving rejects to file data/drivers/drv_net/linux/prlnet.c.rej patching file data/drivers/drv_net/linux/prlnet.h Hunk #1 FAILED at 6. 1 out of 1 hunk FAILED -- saving rejects to file data/drivers/drv_net/linux/prlnet.h.rej patching file data/drivers/drv_virtualnic/vmvirtualnic.c patching file data/drivers/hypervisor/hypercall.h patching file data/drivers/hypervisor/hypervisor.h patching file data/drivers/hypervisor/hypvmstate.c patching file data/drivers/hypervisor/svm_init.h patching file data/drivers/hypervisor/vtx_init.h patching file data/drivers/Makefile ======================================================= PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/portage/app-emulation/parallels-workstation/files/parallels-workstation-2.2.2112-2.6.23.patch ======================================================= can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/compat/compat_memory.h |+++ data/drivers/drv_main/compat/compat_memory.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 19 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/Makefile |+++ data/drivers/drv_main/Makefile -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 25 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/manager.c |+++ data/drivers/drv_main/mm/manager.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 33 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/pages.c |+++ data/drivers/drv_main/mm/pages.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 37 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/vmmain.h |+++ data/drivers/drv_main/vmmain.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 45 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.c |+++ data/drivers/drv_net/linux/prlnet.c -------------------------- No file to patch. Skipping patch. 22 out of 22 hunks ignored can't find file to patch at input line 138 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.h |+++ data/drivers/drv_net/linux/prlnet.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 145 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Только в data/drivers/drv_net/linux: vm-bridge.mod.c |--- data/drivers/drv_virtualnic/vmvirtualnic.c |+++ data/drivers/drv_virtualnic/vmvirtualnic.c -------------------------- No file to patch. Skipping patch. 21 out of 21 hunks ignored can't find file to patch at input line 284 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypercall.h |+++ data/drivers/hypervisor/hypercall.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 299 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypervisor.h |+++ data/drivers/hypervisor/hypervisor.h -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 317 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypvmstate.c |+++ data/drivers/hypervisor/hypvmstate.c -------------------------- No file to patch. Skipping patch. 2 out of 2 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: -------------------------- |--- data/drivers/hypervisor/svm_init.h |+++ data/drivers/hypervisor/svm_init.h -------------------------- No file to patch. Skipping patch. 5 out of 5 hunks ignored can't find file to patch at input line 418 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/vtx_init.h |+++ data/drivers/hypervisor/vtx_init.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 447 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/Makefile |+++ data/drivers/Makefile -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored ======================================================= PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/portage/app-emulation/parallels-workstation/files/parallels-workstation-2.2.2112-2.6.23.patch ======================================================= can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/compat/compat_memory.h |+++ data/drivers/drv_main/compat/compat_memory.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 19 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/Makefile |+++ data/drivers/drv_main/Makefile -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 25 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/manager.c |+++ data/drivers/drv_main/mm/manager.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 33 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/pages.c |+++ data/drivers/drv_main/mm/pages.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 37 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/vmmain.h |+++ data/drivers/drv_main/vmmain.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 45 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.c |+++ data/drivers/drv_net/linux/prlnet.c -------------------------- No file to patch. Skipping patch. 22 out of 22 hunks ignored can't find file to patch at input line 138 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.h |+++ data/drivers/drv_net/linux/prlnet.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 145 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Только в data/drivers/drv_net/linux: vm-bridge.mod.c |--- data/drivers/drv_virtualnic/vmvirtualnic.c |+++ data/drivers/drv_virtualnic/vmvirtualnic.c -------------------------- No file to patch. Skipping patch. 21 out of 21 hunks ignored can't find file to patch at input line 284 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypercall.h |+++ data/drivers/hypervisor/hypercall.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 299 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypervisor.h |+++ data/drivers/hypervisor/hypervisor.h -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 317 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypvmstate.c |+++ data/drivers/hypervisor/hypvmstate.c -------------------------- No file to patch. Skipping patch. 2 out of 2 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: -------------------------- |--- data/drivers/hypervisor/svm_init.h |+++ data/drivers/hypervisor/svm_init.h -------------------------- No file to patch. Skipping patch. 5 out of 5 hunks ignored can't find file to patch at input line 418 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/vtx_init.h |+++ data/drivers/hypervisor/vtx_init.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 447 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/Makefile |+++ data/drivers/Makefile -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored ======================================================= PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/app-emulation/parallels-workstation/files/parallels-workstation-2.2.2112-2.6.23.patch ======================================================= can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/compat/compat_memory.h |+++ data/drivers/drv_main/compat/compat_memory.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 19 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/Makefile |+++ data/drivers/drv_main/Makefile -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 25 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/manager.c |+++ data/drivers/drv_main/mm/manager.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 33 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/pages.c |+++ data/drivers/drv_main/mm/pages.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 37 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/vmmain.h |+++ data/drivers/drv_main/vmmain.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 45 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.c |+++ data/drivers/drv_net/linux/prlnet.c -------------------------- No file to patch. Skipping patch. 22 out of 22 hunks ignored can't find file to patch at input line 138 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.h |+++ data/drivers/drv_net/linux/prlnet.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 145 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Только в data/drivers/drv_net/linux: vm-bridge.mod.c |--- data/drivers/drv_virtualnic/vmvirtualnic.c |+++ data/drivers/drv_virtualnic/vmvirtualnic.c -------------------------- No file to patch. Skipping patch. 21 out of 21 hunks ignored can't find file to patch at input line 284 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypercall.h |+++ data/drivers/hypervisor/hypercall.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 299 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypervisor.h |+++ data/drivers/hypervisor/hypervisor.h -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 317 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypvmstate.c |+++ data/drivers/hypervisor/hypvmstate.c -------------------------- No file to patch. Skipping patch. 2 out of 2 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: -------------------------- |--- data/drivers/hypervisor/svm_init.h |+++ data/drivers/hypervisor/svm_init.h -------------------------- No file to patch. Skipping patch. 5 out of 5 hunks ignored can't find file to patch at input line 418 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/vtx_init.h |+++ data/drivers/hypervisor/vtx_init.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 447 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/Makefile |+++ data/drivers/Makefile -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored ======================================================= PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/portage/app-emulation/parallels-workstation/files/parallels-workstation-2.2.2112-2.6.23.patch ======================================================= can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/compat/compat_memory.h |+++ data/drivers/drv_main/compat/compat_memory.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 19 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/Makefile |+++ data/drivers/drv_main/Makefile -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 25 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/manager.c |+++ data/drivers/drv_main/mm/manager.c -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 33 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/mm/pages.c |+++ data/drivers/drv_main/mm/pages.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 37 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_main/vmmain.h |+++ data/drivers/drv_main/vmmain.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 45 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.c |+++ data/drivers/drv_net/linux/prlnet.c -------------------------- No file to patch. Skipping patch. 22 out of 22 hunks ignored can't find file to patch at input line 138 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/drv_net/linux/prlnet.h |+++ data/drivers/drv_net/linux/prlnet.h -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 145 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Только в data/drivers/drv_net/linux: vm-bridge.mod.c |--- data/drivers/drv_virtualnic/vmvirtualnic.c |+++ data/drivers/drv_virtualnic/vmvirtualnic.c -------------------------- No file to patch. Skipping patch. 21 out of 21 hunks ignored can't find file to patch at input line 284 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypercall.h |+++ data/drivers/hypervisor/hypercall.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 299 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypervisor.h |+++ data/drivers/hypervisor/hypervisor.h -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 317 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/hypvmstate.c |+++ data/drivers/hypervisor/hypvmstate.c -------------------------- No file to patch. Skipping patch. 2 out of 2 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: -------------------------- |--- data/drivers/hypervisor/svm_init.h |+++ data/drivers/hypervisor/svm_init.h -------------------------- No file to patch. Skipping patch. 5 out of 5 hunks ignored can't find file to patch at input line 418 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/hypervisor/vtx_init.h |+++ data/drivers/hypervisor/vtx_init.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 447 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- data/drivers/Makefile |+++ data/drivers/Makefile -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored