automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Junfeng Guo <junfeng.guo@intel.com>, zhoumin@loongson.cn
Subject: |WARNING| pw125981-125990 [PATCH 01/10] net/gve: add Tx queue setup for DQO
Date: Thu, 13 Apr 2023 14:05:31 +0800	[thread overview]
Message-ID: <202304130605.33D65V782764429@localhost.localdomain> (raw)
In-Reply-To: <20230413061650.796940-2-junfeng.guo@intel.com>

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

_apply patch failure_

Submitter: Junfeng Guo <junfeng.guo@intel.com>
Date: Thu, 13 Apr 2023 14:16:41 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 40a62da00b3619ed72be6ceeded89d1fe62ed027

Apply patch set 125981-125990 failed:

Checking patch drivers/net/gve/gve_ethdev.c...
Checking patch drivers/net/gve/gve_ethdev.h...
Hunk #1 succeeded at 25 (offset -3 lines).
Hunk #2 succeeded at 51 (offset -3 lines).
Hunk #3 succeeded at 105 (offset -3 lines).
error: while searching for:
	struct gve_queue_resources *qres;

	/* newly added for DQO */
	uint64_t compl_ring_phys_addr;

	/* Only valid for DQO_RDA queue format */
	struct gve_tx_queue *complq;

error: patch failed: drivers/net/gve/gve_ethdev.h:128
error: drivers/net/gve/gve_ethdev.h: patch does not apply
Checking patch drivers/net/gve/gve_tx_dqo.c...
Checking patch drivers/net/gve/meson.build...


       reply	other threads:[~2023-04-13  6:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230413061650.796940-2-junfeng.guo@intel.com>
2023-04-13  6:05 ` qemudev [this message]
2023-04-13  6:17 ` |SUCCESS| pw125981 " 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=202304130605.33D65V782764429@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).