From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Leo Xu <yongquanx@nvidia.com>
Subject: |WARNING| pw120765-120767 [PATCH 1/3] ethdev: add ICMPv6 id and sequence
Date: Mon, 12 Dec 2022 16:51:46 +0800 [thread overview]
Message-ID: <202212120851.2BC8pkwk1468290@localhost.localdomain> (raw)
In-Reply-To: <20221212085923.2314350-2-yongquanx@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/120765
_apply patch failure_
Submitter: Leo Xu <yongquanx@nvidia.com>
Date: Mon, 12 Dec 2022 10:59:20 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 9351bc0906b4585fd9d50a89f9f6d2f091d3e822
Apply patch set 120765-120767 failed:
Checking patch app/test-pmd/cmdline_flow.c...
Hunk #1 succeeded at 360 (offset -15 lines).
Hunk #2 succeeded at 1333 (offset -46 lines).
Hunk #3 succeeded at 1583 (offset -54 lines).
Hunk #4 succeeded at 4345 (offset -109 lines).
Checking patch doc/guides/prog_guide/rte_flow.rst...
Hunk #1 succeeded at 1165 (offset -95 lines).
Checking patch doc/guides/testpmd_app_ug/testpmd_funcs.rst...
Hunk #1 succeeded at 3648 (offset -385 lines).
Checking patch lib/librte_ethdev/rte_flow.c...
error: lib/librte_ethdev/rte_flow.c: No such file or directory
Checking patch lib/librte_ethdev/rte_flow.h...
error: lib/librte_ethdev/rte_flow.h: No such file or directory
Checking patch lib/librte_net/meson.build...
error: lib/librte_net/meson.build: No such file or directory
Checking patch lib/librte_net/rte_icmp6.h...
next parent reply other threads:[~2022-12-12 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221212085923.2314350-2-yongquanx@nvidia.com>
2022-12-12 8:51 ` qemudev [this message]
2022-12-12 9:01 ` |WARNING| pw120765 " 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=202212120851.2BC8pkwk1468290@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
--cc=yongquanx@nvidia.com \
/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).