automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>, zhoumin@loongson.cn
Subject: |WARNING| pw141491-141507 [PATCH 01/17] net/nfp: refactor speed configuration logic
Date: Mon, 24 Jun 2024 09:32:15 +0800	[thread overview]
Message-ID: <202406240132.45O1WFRN1115079@localhost.localdomain> (raw)
In-Reply-To: <20240624015723.3712898-2-chaoyong.he@corigine.com>

Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/141491

_apply patch failure_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Mon, 24 Jun 2024 09:57:07 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: fbba6db3640f9f623c29c452e1a6b057073e81d2

Apply patch set 141491-141507 failed:

Checking patch drivers/net/nfp/nfp_ethdev.c...
Hunk #1 succeeded at 312 (offset -27 lines).
error: while searching for:
	pf_dev->nfp_eth_table = nfp_eth_table;
	pf_dev->sync = sync;
	pf_dev->total_phyports = nfp_net_get_port_num(pf_dev, nfp_eth_table);

	ret = nfp_net_speed_cap_get(pf_dev);
	if (ret != 0) {

error: patch failed: drivers/net/nfp/nfp_ethdev.c:2250
error: drivers/net/nfp/nfp_ethdev.c: patch does not apply
Checking patch drivers/net/nfp/nfp_net_common.c...
Hunk #1 succeeded at 690 (offset -48 lines).
Checking patch drivers/net/nfp/nfp_net_common.h...
error: while searching for:
	uint8_t vf_base_id;
	/** Number of queues per VF */
	uint32_t queue_per_vf;
};

#define NFP_NET_FLOW_LIMIT    1024

error: patch failed: drivers/net/nfp/nfp_net_common.h:160
error: drivers/net/nfp/nfp_net_common.h: patch does not apply


       reply	other threads:[~2024-06-24  2:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240624015723.3712898-2-chaoyong.he@corigine.com>
2024-06-24  1:32 ` qemudev [this message]
2024-06-24  1:59 ` |SUCCESS| pw141491 " 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=202406240132.45O1WFRN1115079@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).