automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: beilei.xing@intel.com
Subject: |WARNING| pw120556-120570 [PATCH 01/15] common/idpf: add adapter structure
Date: Sat, 10 Dec 2022 11:25:10 +0800	[thread overview]
Message-ID: <202212100325.2BA3PAj41028299@localhost.localdomain> (raw)
In-Reply-To: <20221208075309.37852-2-beilei.xing@intel.com>

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

_apply patch failure_

Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Thu,  8 Dec 2022 07:52:55 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562

Apply patch set 120556-120570 failed:

Checking patch drivers/common/idpf/idpf_common_device.h...
Checking patch drivers/net/idpf/idpf_ethdev.c...
error: while searching for:
			 struct virtchnl2_create_vport *vport_info)
{
	struct idpf_vport *vport = dev->data->dev_private;
	struct idpf_adapter *adapter = vport->adapter;

	vport_info->vport_type = rte_cpu_to_le_16(VIRTCHNL2_VPORT_TYPE_DEFAULT);
	if (adapter->txq_model == 0) {

error: patch failed: drivers/net/idpf/idpf_ethdev.c:138
error: drivers/net/idpf/idpf_ethdev.c: patch does not apply
Checking patch drivers/net/idpf/idpf_ethdev.h...
error: while searching for:
};

struct idpf_vport_param {
	struct idpf_adapter *adapter;
	uint16_t devarg_id; /* arg id from user */
	uint16_t idx;       /* index in adapter->vports[]*/
};

error: patch failed: drivers/net/idpf/idpf_ethdev.h:90
error: drivers/net/idpf/idpf_ethdev.h: patch does not apply
Checking patch drivers/net/idpf/idpf_rxtx.c...
Hunk #4 succeeded at 1782 (offset -9 lines).
Hunk #5 succeeded at 1796 (offset -9 lines).
Hunk #6 succeeded at 2212 (offset -9 lines).
Hunk #7 succeeded at 2266 (offset -9 lines).
Checking patch drivers/net/idpf/idpf_rxtx.h...
Checking patch drivers/net/idpf/idpf_rxtx_vec_avx512.c...
Checking patch drivers/net/idpf/idpf_vchnl.c...
Hunk #5 succeeded at 754 (offset 10 lines).
Hunk #6 succeeded at 847 (offset 10 lines).
Hunk #7 succeeded at 955 (offset 10 lines).
Hunk #8 succeeded at 1026 (offset 10 lines).


      parent reply	other threads:[~2022-12-10  3:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221208075309.37852-2-beilei.xing@intel.com>
2022-12-08  7:54 ` |WARNING| pw120556 " checkpatch
2022-12-08 16:04 ` |WARNING| pw120556-120570 " qemudev
2022-12-08 16:40 ` qemudev
2022-12-10  0:29 ` qemudev
2022-12-10  3:19 ` qemudev
2022-12-10  3: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=202212100325.2BA3PAj41028299@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=beilei.xing@intel.com \
    --cc=test-report@dpdk.org \
    /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).