From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: beilei.xing@intel.com, zhoumin@loongson.cn
Subject: |WARNING| pw125358 [PATCH v2] common/idpf: move PF specific functions from common init
Date: Tue, 21 Mar 2023 15:27:43 +0800 [thread overview]
Message-ID: <202303210727.32L7Rhgj3100304@localhost.localdomain> (raw)
In-Reply-To: <20230321070703.80689-1-beilei.xing@intel.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/125358
_apply patch failure_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Tue, 21 Mar 2023 07:07:03 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: e1071fb9f3740cfca58d4c5fdc430ae68a89eca9
Apply patch set 125358 failed:
Checking patch drivers/common/idpf/idpf_common_device.c...
Checking patch drivers/common/idpf/idpf_common_device.h...
Checking patch drivers/common/idpf/version.map...
Checking patch drivers/net/cpfl/cpfl_ethdev.c...
error: while searching for:
rte_eal_alarm_cancel(cpfl_dev_alarm_handler, adapter);
idpf_adapter_deinit(base);
err_adapter_init:
return ret;
}
error: patch failed: drivers/net/cpfl/cpfl_ethdev.c:1213
error: drivers/net/cpfl/cpfl_ethdev.c: patch does not apply
Checking patch drivers/net/idpf/idpf_ethdev.c...
error: while searching for:
rte_eal_alarm_cancel(idpf_dev_alarm_handler, adapter);
idpf_adapter_deinit(base);
err_adapter_init:
return ret;
}
error: patch failed: drivers/net/idpf/idpf_ethdev.c:1175
error: drivers/net/idpf/idpf_ethdev.c: patch does not apply
next parent reply other threads:[~2023-03-21 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230321070703.80689-1-beilei.xing@intel.com>
2023-03-21 7:27 ` qemudev [this message]
2023-03-21 7:40 ` |SUCCESS| " checkpatch
2023-03-21 10:20 ` |FAILURE| " 0-day Robot
2023-03-21 15:21 |WARNING| pw125358 [PATCH] [v2] " dpdklab
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=202303210727.32L7Rhgj3100304@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=beilei.xing@intel.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).