automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Wenjing Qiao <wenjing.qiao@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw130151-130154 [PATCH v2 1/4] net/cpfl: parse flow parser file in devargs
Date: Fri, 11 Aug 2023 19:25:15 +0800	[thread overview]
Message-ID: <202308111125.37BBPFtx3598165@localhost.localdomain> (raw)
In-Reply-To: <20230811100012.2078135-2-wenjing.qiao@intel.com>

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

_apply patch failure_

Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Fri, 11 Aug 2023 10:00:11 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 70b6941e4e22d67bc10495d1638234a7e974f582

Apply patch set 130151-130154 failed:

Checking patch drivers/net/cpfl/cpfl_ethdev.c...
Hunk #1 succeeded at 17 (offset -4 lines).
Hunk #2 succeeded at 28 (offset -5 lines).
error: while searching for:
	return 0;
}

static int
cpfl_parse_devargs(struct rte_pci_device *pci_dev, struct cpfl_adapter_ext *adapter, bool first)
{

error: patch failed: drivers/net/cpfl/cpfl_ethdev.c:1671
error: drivers/net/cpfl/cpfl_ethdev.c: patch does not apply
Checking patch drivers/net/cpfl/cpfl_ethdev.h...
error: while searching for:
#define ACC_LCE_ID	15
#define IMC_MBX_EFD_ID	0

struct cpfl_vport_param {
	struct cpfl_adapter_ext *adapter;
	uint16_t devarg_id; /* arg id from user */

error: patch failed: drivers/net/cpfl/cpfl_ethdev.h:87
error: drivers/net/cpfl/cpfl_ethdev.h: patch does not apply
Checking patch drivers/net/cpfl/meson.build...
Hunk #1 succeeded at 36 (offset -2 lines).


      parent reply	other threads:[~2023-08-11 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230811100012.2078135-2-wenjing.qiao@intel.com>
2023-08-11 10:07 ` |SUCCESS| pw130151 " checkpatch
2023-08-11 11:25 ` qemudev [this message]

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=202308111125.37BBPFtx3598165@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=test-report@dpdk.org \
    --cc=wenjing.qiao@intel.com \
    --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).