automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Sunyang Wu <sunyang.wu@jaguarmicro.com>, zhoumin@loongson.cn
Subject: |WARNING| pw153350 回复: [PATCH] ethdev: optimize how the values of the flag variables are assigned
Date: Thu, 8 May 2025 13:56:57 +0800	[thread overview]
Message-ID: <202505080556.5485uvnL3839997@localhost.localdomain> (raw)
In-Reply-To: <KL1PR0601MB55678B1F0A4D7AC99B21B5F6908BA@KL1PR0601MB5567.apcprd06.prod.outlook.com>

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

_apply patch failure_

Submitter: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Date: Thu, 8 May 2025 06:26:39 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: ff05ee3e3f8fb4ce958a2ce6461e8141aea959c6

Apply patch set 153350 failed:

Checking patch lib/ethdev/rte_ethdev.c...
error: while searching for:
       if (dev->dev_ops->promiscuous_disable == NULL)
               return -ENOTSUP;

       dev->data->promiscuous = 0;
       diag = dev->dev_ops->promiscuous_disable(dev);
       if (diag != 0)
               dev->data->promiscuous = 1;

       diag = eth_err(port_id, diag);


error: patch failed: lib/ethdev/rte_ethdev.c:3044
error: lib/ethdev/rte_ethdev.c: patch does not apply


       reply	other threads:[~2025-05-08  6:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <KL1PR0601MB55678B1F0A4D7AC99B21B5F6908BA@KL1PR0601MB5567.apcprd06.prod.outlook.com>
2025-05-08  5:56 ` qemudev [this message]
2025-05-08  9:49 ` |WARNING| pw153350 [PATCH] Hui Fu : " dpdklab
2025-05-08 10:48 ` 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=202505080556.5485uvnL3839997@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=sunyang.wu@jaguarmicro.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).