automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Hanumanth Pothula <hpothula@marvell.com>
Subject: |WARNING| pw119933 [PATCH v1 1/1] app/testpmd: add valid check to verify multi mempool feature
Date: Thu, 17 Nov 2022 19:22:15 +0800	[thread overview]
Message-ID: <202211171122.2AHBMFYW2616047@localhost.localdomain> (raw)
In-Reply-To: <20221117113047.3088461-1-hpothula@marvell.com>

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

_apply patch failure_

Submitter: Hanumanth Pothula <hpothula@marvell.com>
Date: Thu, 17 Nov 2022 17:00:47 +0530
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 04f68bb92b6fee621ddf0f0948f5565fa31a84fd

Apply patch set 119933 failed:

Checking patch app/test-pmd/testpmd.c...
error: while searching for:
{
	union rte_eth_rxseg rx_useg[MAX_SEGS_BUFFER_SPLIT] = {};
	struct rte_mempool *rx_mempool[MAX_MEMPOOL] = {};
	struct rte_mempool *mpx;
	unsigned int i, mp_n;
	int ret;

	/* Verify Rx queue configuration is single pool and segment or
	 * multiple pool/segment.
	 * @see rte_eth_rxconf::rx_mempools
	 * @see rte_eth_rxconf::rx_seg
	 */
	if (!(mbuf_data_size_n > 1) && !(rx_pkt_nb_segs > 1 ||
	    ((rx_conf->offloads & RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT) != 0))) {
		/* Single pool/segment configuration */
		rx_conf->rx_seg = NULL;

error: patch failed: app/test-pmd/testpmd.c:2648
error: app/test-pmd/testpmd.c: patch does not apply


       reply	other threads:[~2022-11-17 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221117113047.3088461-1-hpothula@marvell.com>
2022-11-17 11:22 ` qemudev [this message]
2022-11-17 11:31 ` |SUCCESS| " checkpatch
2022-11-17 11:48 |WARNING| pw119933 [PATCH] [v1, " dpdklab

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=202211171122.2AHBMFYW2616047@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=hpothula@marvell.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).