From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>, zhoumin@loongson.cn
Subject: |WARNING| pw143606-143613 [PATCH 1/8] net/nfp: fix incorrect type declaration of some variables
Date: Thu, 5 Sep 2024 14:00:00 +0800 [thread overview]
Message-ID: <202409050600.485600gD1217019@localhost.localdomain> (raw)
In-Reply-To: <20240905062511.2710102-2-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/143606
_apply patch failure_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thu, 5 Sep 2024 14:25:04 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 5cce3d463a99dbb5e7797faaed6c68df6c2b549a
Apply patch set 143606-143613 failed:
Checking patch drivers/net/nfp/nfp_net_common.c...
Hunk #1 succeeded at 776 (offset -1 lines).
error: while searching for:
uint32_t link_status)
{
int ret;
uint32_t nn_link_status;
struct nfp_net_hw_priv *hw_priv;
hw_priv = dev->process_private;
if (link->link_status == RTE_ETH_LINK_UP) {
if (hw_priv->is_pf) {
nfp_net_speed_aneg_update(dev, hw, hw_priv, link);
} else {
/*
* Shift and mask nn_link_status so that it is effectively the value
* at offset NFP_NET_CFG_STS_NSP_LINK_RATE.
*/
nn_link_status = (link_status >> NFP_NET_CFG_STS_LINK_RATE_SHIFT) &
NFP_NET_CFG_STS_LINK_RATE_MASK;
if (nn_link_status < RTE_DIM(nfp_net_link_speed_nfp2rte))
link->link_speed = nfp_net_link_speed_nfp2rte[nn_link_status];
}
}
ret = rte_eth_linkstatus_set(dev, link);
error: patch failed: drivers/net/nfp/nfp_net_common.c:784
error: drivers/net/nfp/nfp_net_common.c: patch does not apply
next parent reply other threads:[~2024-09-05 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905062511.2710102-2-chaoyong.he@corigine.com>
2024-09-05 6:00 ` qemudev [this message]
2024-09-05 6:27 ` |SUCCESS| pw143606 " 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=202409050600.485600gD1217019@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).