From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>, zhoumin@loongson.cn
Subject: |WARNING| pw142195-142198 [PATCH v2 1/4] net/nfp: export more interfaces of NFDk
Date: Mon, 8 Jul 2024 13:45:15 +0800 [thread overview]
Message-ID: <202407080545.4685jFle2283143@localhost.localdomain> (raw)
In-Reply-To: <20240708055854.107739-2-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/142195
_apply patch failure_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Mon, 8 Jul 2024 13:58:51 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 249c34811d8f134110784872ee3f31ead1fde84c
Apply patch set 142195-142198 failed:
Checking patch drivers/net/nfp/meson.build...
error: while searching for:
'nfp_net_flow.c',
'nfp_net_meta.c',
'nfp_rxtx.c',
'nfp_service.c',
'nfp_trace.c',
)
deps += ['hash', 'security', 'common_nfp']
error: patch failed: drivers/net/nfp/meson.build:43
error: drivers/net/nfp/meson.build: patch does not apply
Checking patch drivers/net/nfp/nfdk/nfp_nfdk.h...
Checking patch drivers/net/nfp/nfdk/nfp_nfdk_dp.c...
Checking patch drivers/net/nfp/nfdk/nfp_nfdk_vec.h...
Checking patch drivers/net/nfp/nfdk/nfp_nfdk_vec_avx2_dp.c...
Checking patch drivers/net/nfp/nfdk/nfp_nfdk_vec_stub.c...
Checking patch drivers/net/nfp/nfp_ethdev.c...
Checking patch drivers/net/nfp/nfp_ethdev_vf.c...
Checking patch drivers/net/nfp/nfp_rxtx.h...
Checking patch drivers/net/nfp/nfp_rxtx_vec.h...
Checking patch drivers/net/nfp/nfp_rxtx_vec_avx2.c...
Checking patch drivers/net/nfp/nfp_rxtx_vec_stub.c...
next parent reply other threads:[~2024-07-08 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240708055854.107739-2-chaoyong.he@corigine.com>
2024-07-08 5:45 ` qemudev [this message]
2024-07-08 6:00 ` |SUCCESS| pw142195 " 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=202407080545.4685jFle2283143@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=chaoyong.he@corigine.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).