From: sys_stv@intel.com
To: test-report@dpdk.org, francesco.mancino@tutus.se
Subject: [dpdk-test-report] |WARNING| pw(114721) sid(24226) job(PER_PATCH_BUILD3765)[v4] net/tap: Allow jumbo frames
Date: 08 Aug 2022 05:12:45 -0700 [thread overview]
Message-ID: <e2f6d4$ht7669@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/114721
_apply issues_
Submitter: Francesco Mancino <francesco.mancino@tutus.se>
Date: 2022-08-08 12:07:04
Reply_mail: <dc63d801-2685-1bd4-9b6a-dbc01a49c8f7@tutus.se>
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 72206323a5dd3182b13f61b25a64abdddfee595c
Repo:dpdk, CommitID: 72206323a5dd3182b13f61b25a64abdddfee595c
* Repo: dpdk-next-net
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/net/tap/rte_eth_tap.c:1066
error: drivers/net/tap/rte_eth_tap.c: patch does not apply
Applying: net/tap: Allow jumbo frames
Patch failed at 0001 net/tap: Allow jumbo frames
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/net/tap/rte_eth_tap.c:1066
error: drivers/net/tap/rte_eth_tap.c: patch does not apply
Applying: net/tap: Allow jumbo frames
Patch failed at 0001 net/tap: Allow jumbo frames
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:[~2022-08-08 12:12 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='e2f6d4$ht7669@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=francesco.mancino@tutus.se \
--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).