automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Suanming Mou <suanmingm@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw135319-135320 [PATCH v2 1/3] ethdev: rename action modify field data structure
Date: Tue, 19 Dec 2023 09:14:04 +0800	[thread overview]
Message-ID: <202312190114.3BJ1E4vI2987174@localhost.localdomain> (raw)
In-Reply-To: <20231219013337.531548-2-suanmingm@nvidia.com>

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

_apply patch failure_

Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Tue, 19 Dec 2023 09:33:35 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 84bfce561f24a33cb186efdc1cf8dc4a8c96fd26

Apply patch set 135319-135320 failed:

Checking patch app/test-pmd/cmdline_flow.c...
Checking patch doc/guides/nics/features/default.ini...
Checking patch doc/guides/prog_guide/rte_flow.rst...
Checking patch doc/guides/rel_notes/release_24_03.rst...
error: while searching for:
     Also, make sure to start the actual text at the margin.
     =======================================================

* **Updated NVIDIA mlx5 driver.**

  * Added support for accumulating from src field to dst field.

error: patch failed: doc/guides/rel_notes/release_24_03.rst:55
error: doc/guides/rel_notes/release_24_03.rst: patch does not apply
Checking patch doc/guides/testpmd_app_ug/testpmd_funcs.rst...
Hunk #1 succeeded at 3852 (offset 11 lines).
Checking patch lib/ethdev/rte_flow.c...
Checking patch lib/ethdev/rte_flow.h...


       reply	other threads:[~2023-12-19  1:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231219013337.531548-2-suanmingm@nvidia.com>
2023-12-19  1:14 ` qemudev [this message]
2023-12-19  1:35 ` |SUCCESS| pw135319 " 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=202312190114.3BJ1E4vI2987174@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=suanmingm@nvidia.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).