From: sys_stv@intel.com
To: test-report@dpdk.org, martin.weiser@allegro-packets.com
Subject: compilation|WARNING| pw(147513) sid(33731) job(PER_PATCH_BUILD13914)igc: fix invalid length and corrupted multi-segment mbufs
Date: 28 Oct 2024 07:03:53 -0700 [thread overview]
Message-ID: <68906f$2ic123@ORVIESA003-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/147513
_apply issues_
Submitter: Martin Weiser <martin.weiser@allegro-packets.com>
Date: 2024-10-28 13:51:23
Reply_mail: <5f0486a2-eb1e-4349-bdca-ee2c241379b3@allegro-packets.com>
DPDK git baseline:
Repo:dpdk-next-net-intel, CommitID: 69c0ffb893fa9c1c7b00947a2801cef50ebc65d4
Repo:dpdk, CommitID: 6dad0bb5c8621644beca86ff5f4910a943ba604d
* Repo: dpdk-next-net-intel
This will be required in git-pw 2.0
error: patch fragment without header at line 6: @@ -509,6 +511,12 @@ igc_recv_scattered_pkts(void *rx_queue, struct
Applying: igc: fix invalid length and corrupted multi-segment mbufs
Patch failed at 0001 igc: fix invalid length and corrupted multi-segment mbufs
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
error: patch fragment without header at line 6: @@ -509,6 +511,12 @@ igc_recv_scattered_pkts(void *rx_queue, struct
Applying: igc: fix invalid length and corrupted multi-segment mbufs
Patch failed at 0001 igc: fix invalid length and corrupted multi-segment mbufs
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:[~2024-10-28 14: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='68906f$2ic123@ORVIESA003-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=martin.weiser@allegro-packets.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).