From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Dengdui Huang <huangdengdui@huawei.com>, zhoumin@loongson.cn
Subject: |WARNING| pw147907-147950 [PATCH v5 01/52] eal: fix use rte errno for libc function
Date: Mon, 4 Nov 2024 18:46:35 +0800 [thread overview]
Message-ID: <202411041046.4A4AkZSf3462689@localhost.localdomain> (raw)
In-Reply-To: <20241104111037.3632161-2-huangdengdui@huawei.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/147907
_apply patch failure_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Mon, 4 Nov 2024 19:09:46 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: c79900e31e3e5a16c7f5410d0800315a0491ccad
Apply patch set 147907-147950 failed:
Checking patch drivers/net/tap/rte_eth_tap.c...
Hunk #1 succeeded at 154 (offset 1 line).
Hunk #2 succeeded at 198 (offset 1 line).
Hunk #3 succeeded at 229 (offset 1 line).
Hunk #4 succeeded at 306 (offset 1 line).
Hunk #5 succeeded at 799 (offset 1 line).
Hunk #6 succeeded at 839 (offset 1 line).
Hunk #7 succeeded at 1929 (offset -4 lines).
Hunk #8 succeeded at 1965 (offset -3 lines).
Hunk #9 succeeded at 2131 (offset -2 lines).
Hunk #10 succeeded at 2144 (offset -2 lines).
Checking patch drivers/net/tap/tap_flow.c...
error: while searching for:
{
struct pmd_internals *pmd = dev->data->dev_private;
struct rte_flow *remote_flow = NULL;
struct rte_flow *flow = NULL;
struct tap_nlmsg *msg = NULL;
int err;
error: patch failed: drivers/net/tap/tap_flow.c:1258
error: drivers/net/tap/tap_flow.c: patch does not apply
Checking patch drivers/net/tap/tap_netlink.c...
Checking patch drivers/net/tap/tap_tcmsgs.c...
next parent reply other threads:[~2024-11-04 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241104111037.3632161-2-huangdengdui@huawei.com>
2024-11-04 10:46 ` qemudev [this message]
2024-11-04 11:10 ` |SUCCESS| pw147907 " 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=202411041046.4A4AkZSf3462689@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=huangdengdui@huawei.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).