From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>, zhoumin@loongson.cn
Subject: |WARNING| pw132371-132381 [PATCH 01/11] net/nfp: explicitly compare to null and 0
Date: Sat, 7 Oct 2023 10:16:49 +0800 [thread overview]
Message-ID: <202310070216.3972GnSb887083@localhost.localdomain> (raw)
In-Reply-To: <20231007023339.1546659-2-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/132371
_apply patch failure_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Sat, 7 Oct 2023 10:33:29 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 40435075a790fac6e5d5ad7a967950f5e56e45c8
Apply patch set 132371-132381 failed:
Checking patch drivers/net/nfp/flower/nfp_flower.c...
Checking patch drivers/net/nfp/nfd3/nfp_nfd3_dp.c...
Checking patch drivers/net/nfp/nfp_common.c...
Checking patch drivers/net/nfp/nfp_common.h...
Checking patch drivers/net/nfp/nfp_cpp_bridge.c...
Checking patch drivers/net/nfp/nfp_ethdev.c...
Checking patch drivers/net/nfp/nfp_ethdev_vf.c...
Checking patch drivers/net/nfp/nfp_flow.c...
error: while searching for:
struct nfp_fl_key_ls *key_layer,
uint32_t stats_ctx)
{
struct nfp_fl_rule_metadata *nfp_flow_meta;
char *mbuf_off_exact;
char *mbuf_off_mask;
/*
* Convert to long words as firmware expects
error: patch failed: drivers/net/nfp/nfp_flow.c:728
error: drivers/net/nfp/nfp_flow.c: patch does not apply
Checking patch drivers/net/nfp/nfp_rxtx.c...
next parent reply other threads:[~2023-10-07 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231007023339.1546659-2-chaoyong.he@corigine.com>
2023-10-07 2:16 ` qemudev [this message]
2023-10-07 2:35 ` |SUCCESS| pw132371 " 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=202310070216.3972GnSb887083@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).