From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Junfeng Guo <junfeng.guo@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw122226-122233 [RFC 1/8] net/gve: add Rx queue setup for DQO
Date: Wed, 18 Jan 2023 11:40:23 +0800 [thread overview]
Message-ID: <202301180340.30I3eNtp1992425@localhost.localdomain> (raw)
In-Reply-To: <20230118025347.1567078-2-junfeng.guo@intel.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/122226
_apply patch failure_
Submitter: Junfeng Guo <junfeng.guo@intel.com>
Date: Wed, 18 Jan 2023 10:53:40 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: b81d4cec2995cc109933456323677816b2aea1a6
Apply patch set 122226-122233 failed:
Checking patch drivers/net/gve/gve_ethdev.c...
error: while searching for:
{
/* override eth_dev ops for DQO */
local_eth_dev_ops->tx_queue_setup = gve_tx_queue_setup_dqo;
}
static void
error: patch failed: drivers/net/gve/gve_ethdev.c:366
error: drivers/net/gve/gve_ethdev.c: patch does not apply
Checking patch drivers/net/gve/gve_ethdev.h...
Hunk #1 succeeded at 121 (offset -24 lines).
Hunk #2 succeeded at 140 (offset -24 lines).
error: while searching for:
/* Below functions are used for DQO */
int
gve_tx_queue_setup_dqo(struct rte_eth_dev *dev, uint16_t queue_id,
uint16_t nb_desc, unsigned int socket_id,
error: patch failed: drivers/net/gve/gve_ethdev.h:334
error: drivers/net/gve/gve_ethdev.h: patch does not apply
Checking patch drivers/net/gve/gve_rx_dqo.c...
Checking patch drivers/net/gve/meson.build...
error: while searching for:
'base/gve_adminq.c',
'gve_rx.c',
'gve_tx.c',
'gve_tx_dqo.c',
'gve_ethdev.c',
)
error: patch failed: drivers/net/gve/meson.build:11
error: drivers/net/gve/meson.build: patch does not apply
prev parent reply other threads:[~2023-01-18 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230118025347.1567078-2-junfeng.guo@intel.com>
2023-01-18 3:00 ` |WARNING| pw122226 " checkpatch
2023-01-18 3:40 ` 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=202301180340.30I3eNtp1992425@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=junfeng.guo@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).