From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw137961 [PATCH] RFC: Using and renaming 8-bit reserved field of rte_crypto_op for implementation specific
Date: Mon, 04 Mar 2024 23:40:02 -0800 (PST) [thread overview]
Message-ID: <65e6cc52.050a0220.30d56.95e1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <MW4PR11MB59115297140DB034BD39047187222@MW4PR11MB5911.namprd11.prod.outlook.com>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/137961
_apply patch failure_
Submitter: Kundapura, Ganapati <ganapati.kundapura@intel.com>
Date: Tuesday, March 05 2024 07:13:33
Applied on: CommitID:be793709e7b044cd4f806d6103bf3c046311a3c7
Apply patch set 137961 failed:
Cloning the DPDK mirror at: https://github.com/DPDK/dpdk.git (Attempt 1 of 3)
Trying to checkout branch: main
Checked out to main (be793709e7b044cd4f806d6103bf3c046311a3c7)
Done: main commit be793709e7b044cd4f806d6103bf3c046311a3c7
Trying to checkout branch: origin/next-crypto-for-main
Checked out to next-crypto-for-main (be793709e7b044cd4f806d6103bf3c046311a3c7)
Applying patch...
Failed to apply patch:
Applying: RFC: Using and renaming 8-bit reserved field of rte_crypto_op for implementation specific
error: corrupt patch at line 20
error: could not build fake ancestor
hint: Use 'git am --show-current-patch' to see the failed patch
Patch failed at 0001 RFC: Using and renaming 8-bit reserved field of rte_crypto_op for implementation specific
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".
Trying to checkout branch: main
Checked out to main (be793709e7b044cd4f806d6103bf3c046311a3c7)
Applying patch...
Failed to apply patch:
Applying: RFC: Using and renaming 8-bit reserved field of rte_crypto_op for implementation specific
error: corrupt patch at line 20
error: could not build fake ancestor
hint: Use 'git am --show-current-patch' to see the failed patch
Patch failed at 0001 RFC: Using and renaming 8-bit reserved field of rte_crypto_op for implementation specific
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".
https://lab.dpdk.org/results/dashboard/patchsets/29409/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2024-03-05 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MW4PR11MB59115297140DB034BD39047187222@MW4PR11MB5911.namprd11.prod.outlook.com>
2024-03-05 6:53 ` |WARNING| pw137961 " qemudev
2024-03-05 7:40 ` dpdklab [this message]
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=65e6cc52.050a0220.30d56.95e1SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).