From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw134411 [PATCH] [v2] net/axgbe: support TSO
Date: Thu, 16 Nov 2023 02:02:11 -0800 (PST) [thread overview]
Message-ID: <6555e8a3.5d0a0220.6a0ab.7a8fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/134411
_apply patch failure_
Submitter: Jesna K E <jesna.k.e@amd.com>
Date: Thursday, November 16 2023 09:44:46
Applied on: CommitID:a7bacafd92ce9769d5b22b13406687f851152549
Apply patch set 134411 failed:
Checking patch doc/guides/nics/features/axgbe.ini...
Checking patch drivers/net/axgbe/axgbe_common.h...
Checking patch drivers/net/axgbe/axgbe_dev.c...
Checking patch drivers/net/axgbe/axgbe_ethdev.c...
error: while searching for:
#include "eal_filesystem.h"
#ifdef RTE_ARCH_X86
#include <cpuid.h>
#else
error: patch failed: drivers/net/axgbe/axgbe_ethdev.c:12
Checking patch drivers/net/axgbe/axgbe_ethdev.h...
Checking patch drivers/net/axgbe/axgbe_rxtx.c...
Applied patch doc/guides/nics/features/axgbe.ini cleanly.
Applied patch drivers/net/axgbe/axgbe_common.h cleanly.
Applied patch drivers/net/axgbe/axgbe_dev.c cleanly.
Applying patch drivers/net/axgbe/axgbe_ethdev.c with 1 reject...
Rejected hunk #1.
Hunk #2 applied cleanly.
Applied patch drivers/net/axgbe/axgbe_ethdev.h cleanly.
Applied patch drivers/net/axgbe/axgbe_rxtx.c cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/drivers/net/axgbe/axgbe_ethdev.c b/drivers/net/axgbe/axgbe_ethdev.c (rejected hunks)
@@ -12,6 +12,8 @@
#include "eal_filesystem.h"
+#include <rte_vect.h>
+
#ifdef RTE_ARCH_X86
#include <cpuid.h>
#else
https://lab.dpdk.org/results/dashboard/patchsets/28394/
UNH-IOL DPDK Community Lab
next reply other threads:[~2023-11-16 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 10:02 dpdklab [this message]
[not found] <20231116094446.62248-1-jesna.k.e@amd.com>
2023-11-16 9:45 ` |WARNING| pw134411 [PATCH v2] " checkpatch
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=6555e8a3.5d0a0220.6a0ab.7a8fSMTPIN_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).