From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: beilei.xing@intel.com, zhoumin@loongson.cn
Subject: |WARNING| pw121663-121675 [PATCH v2 01/15] common/idpf: add adapter structure
Date: Fri, 6 Jan 2023 17:35:37 +0800 [thread overview]
Message-ID: <202301060935.3069ZbkJ4143903@localhost.localdomain> (raw)
In-Reply-To: <20230106091627.13530-2-beilei.xing@intel.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/121663
_apply patch failure_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Fri, 6 Jan 2023 09:16:13 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 43d326b6f923f32473f550228910e1bd5de3f3fb
Apply patch set 121663-121675 failed:
Checking patch drivers/common/idpf/idpf_common_device.h...
Checking patch drivers/net/idpf/idpf_ethdev.c...
error: while searching for:
struct idpf_vport *vport = dev->data->dev_private;
struct idpf_adapter *adapter = vport->adapter;
dev_info->max_rx_queues = adapter->caps->max_rx_q;
dev_info->max_tx_queues = adapter->caps->max_tx_q;
dev_info->min_rx_bufsize = IDPF_MIN_BUF_SIZE;
dev_info->max_rx_pktlen = vport->max_mtu + IDPF_ETH_OVERHEAD;
error: patch failed: drivers/net/idpf/idpf_ethdev.c:53
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:91
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).
next prev parent reply other threads:[~2023-01-06 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230106091627.13530-2-beilei.xing@intel.com>
2023-01-06 9:32 ` qemudev
2023-01-06 9:35 ` qemudev [this message]
2023-01-06 9:42 ` |WARNING| pw121663 " 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=202301060935.3069ZbkJ4143903@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=beilei.xing@intel.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).