From: sys_stv@intel.com
To: test-report@dpdk.org, kai.ji@intel.com
Subject: [dpdk-test-report] |WARNING| pw(103496) sid(20222) job(PER_PATCH_BUILD9396)[v3, 8/8] crypto/qat: qat driver rework clean up
Date: 02 Nov 2021 12:04:33 -0700 [thread overview]
Message-ID: <722c05$eii9ob@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/103496
_apply issues_
Submitter: Kai Ji <kai.ji@intel.com>
Date: 2021-11-02 13:49:13
Reply_mail: 20211102134913.21148-9-kai.ji@intel.com
DPDK git baseline:
Repo:dpdk-next-crypto, CommitID: e7931ac1505a47a42ff338cc6ea3e0e424590999
Repo:dpdk, CommitID: f88b0b892204d071a46a629b00424a8d47055ba4
* Repo: dpdk-next-crypto
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: drivers/common/qat/qat_qp.c:549
error: drivers/common/qat/qat_qp.c: patch does not apply
error: patch failed: drivers/common/qat/qat_qp.h:77
error: drivers/common/qat/qat_qp.h: patch does not apply
Applying: crypro/qat: qat driver refactor skeleton
Patch failed at 0001 crypro/qat: qat driver refactor skeleton
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
* Repo: dpdk
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: drivers/common/qat/qat_qp.c:549
error: drivers/common/qat/qat_qp.c: patch does not apply
error: patch failed: drivers/common/qat/qat_qp.h:77
error: drivers/common/qat/qat_qp.h: patch does not apply
Applying: crypro/qat: qat driver refactor skeleton
Patch failed at 0001 crypro/qat: qat driver refactor skeleton
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2021-11-02 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='722c05$eii9ob@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=kai.ji@intel.com \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).