[dpdk-test-report] |FAILURE| pw38156 [PATCH v10 02/10] crypto/virtio: support virtio device init

sys_stv at intel.com sys_stv at intel.com
Thu Apr 26 23:04:48 CEST 2018

Previous message: [dpdk-test-report] |FAILURE| pw38161 [PATCH v10 10/10] doc: add virtio crypto PMD guide
Next message: [dpdk-test-report] |SUCCESS| pw39059 [PATCH 11/13] app/bbdev: added new test vectors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38156

_apply patch file failure_

Submitter: Jay Zhou <jianjay.zhou at huawei.com>
Date: Mon, 16 Apr 2018 10:21:23 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
                   Repo:dpdk-next-crypto, Branch:master, CommitID:eb8a86e275ef15a5455948d679d1a2c43dd4c740
                   Repo:dpdk-next-net, Branch:master, CommitID:e657a5d5fae02bcd8e62d4e57338d7d363e638c1
                   Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
                   Repo:dpdk, Branch:master, CommitID:09f4aa2b955f9f9e2e662ca7c5f3fa7258ef4614
                   
Apply patch file failed:
Repo: dpdk
38156:
patching file drivers/crypto/virtio/Makefile
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/crypto/virtio/Makefile.rej
patching file drivers/crypto/virtio/meson.build
Hunk #1 FAILED at 6.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/meson.build.rej
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 3.
Hunk #2 FAILED at 34.
2 out of 2 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 FAILED at 5.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.h.rej
The next patch would create the file drivers/crypto/virtio/virtio_logs.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_pci.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_pci.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_ring.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_rxtx.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtqueue.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtqueue.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored

Repo: dpdk-next-crypto
38156:
patching file drivers/crypto/virtio/Makefile
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/crypto/virtio/Makefile.rej
patching file drivers/crypto/virtio/meson.build
Hunk #1 FAILED at 6.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/meson.build.rej
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 3.
Hunk #2 FAILED at 34.
2 out of 2 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 FAILED at 5.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.h.rej
The next patch would create the file drivers/crypto/virtio/virtio_logs.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_pci.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_pci.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_ring.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_rxtx.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtqueue.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtqueue.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored

Repo: dpdk-next-net
38156:
patching file drivers/crypto/virtio/Makefile
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/crypto/virtio/Makefile.rej
patching file drivers/crypto/virtio/meson.build
Hunk #1 FAILED at 6.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/meson.build.rej
patching file drivers/crypto/virtio/virtio_cryptodev.c
Hunk #1 FAILED at 3.
Hunk #2 FAILED at 34.
2 out of 2 hunks FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.c.rej
patching file drivers/crypto/virtio/virtio_cryptodev.h
Hunk #1 FAILED at 5.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/virtio/virtio_cryptodev.h.rej
The next patch would create the file drivers/crypto/virtio/virtio_logs.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_pci.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_pci.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_ring.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtio_rxtx.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtqueue.c,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/crypto/virtio/virtqueue.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored


DPDK STV team

Previous message: [dpdk-test-report] |FAILURE| pw38161 [PATCH v10 10/10] doc: add virtio crypto PMD guide
Next message: [dpdk-test-report] |SUCCESS| pw39059 [PATCH 11/13] app/bbdev: added new test vectors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the test-report mailing list