From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, zhoumin@loongson.cn
Subject: |WARNING| pw136480-136485 [PATCH v3 1/6] ethdev: add modify IPv4 next protocol field
Date: Wed, 7 Feb 2024 20:10:35 +0800 [thread overview]
Message-ID: <202402071210.417CAZQ0674299@localhost.localdomain> (raw)
In-Reply-To: <20240207122908.20646-1-viacheslavo@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/136480
_apply patch failure_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Wed, 7 Feb 2024 14:29:03 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: cf027b7c76a125aa2a040488cc60f9c4356c0166
Apply patch set 136480-136485 failed:
Checking patch doc/guides/rel_notes/release_24_03.rst...
error: while searching for:
* Added HW steering support for modify field ``RTE_FLOW_FIELD_GENEVE_OPT_TYPE`` flow action.
* Added HW steering support for modify field ``RTE_FLOW_FIELD_GENEVE_OPT_CLASS`` flow action.
* Added HW steering support for modify field ``RTE_FLOW_FIELD_GENEVE_OPT_DATA`` flow action.
Removed Items
error: patch failed: doc/guides/rel_notes/release_24_03.rst:108
error: doc/guides/rel_notes/release_24_03.rst: patch does not apply
Checking patch drivers/common/mlx5/mlx5_prm.h...
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
Hunk #1 succeeded at 1365 (offset -19 lines).
Hunk #2 succeeded at 2049 (offset -146 lines).
next parent reply other threads:[~2024-02-07 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240207122908.20646-1-viacheslavo@nvidia.com>
2024-02-07 12:10 ` qemudev [this message]
2024-02-07 12:31 ` |WARNING| pw136480 " 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=202402071210.417CAZQ0674299@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
--cc=viacheslavo@nvidia.com \
--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).