From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: <psatheesh@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw135203-135205 [PATCH v2 1/3] common/cnxk: support mirror flow action
Date: Thu, 14 Dec 2023 22:31:01 +0800 [thread overview]
Message-ID: <202312141431.3BEEV1TF1109694@localhost.localdomain> (raw)
In-Reply-To: <20231214145016.571806-1-psatheesh@marvell.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/135203
_apply patch failure_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Thu, 14 Dec 2023 20:20:14 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: a37132a27ff8941316ca1a0194ba72780d22abfd
Apply patch set 135203-135205 failed:
Checking patch doc/guides/nics/features/cnxk.ini...
Hunk #1 succeeded at 96 (offset -1 lines).
Checking patch doc/guides/rel_notes/release_24_03.rst...
error: while searching for:
* **Updated Marvell cnxk net driver.**
* Added support for ``RTE_FLOW_ITEM_TYPE_PPPOES`` flow item.
Removed Items
-------------
error: patch failed: doc/guides/rel_notes/release_24_03.rst:65
error: doc/guides/rel_notes/release_24_03.rst: patch does not apply
Checking patch drivers/net/cnxk/cnxk_flow.c...
Hunk #1 succeeded at 113 (offset -1 lines).
Hunk #2 succeeded at 324 (offset -1 lines).
Hunk #3 succeeded at 362 (offset -1 lines).
Hunk #4 succeeded at 383 (offset -1 lines).
Hunk #5 succeeded at 395 (offset -1 lines).
Hunk #6 succeeded at 409 (offset -1 lines).
Hunk #7 succeeded at 439 (offset -1 lines).
Hunk #8 succeeded at 447 (offset -1 lines).
next parent reply other threads:[~2023-12-14 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231214145016.571806-1-psatheesh@marvell.com>
2023-12-14 14:31 ` qemudev [this message]
2023-12-14 14:51 ` |SUCCESS| pw135203 " 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=202312141431.3BEEV1TF1109694@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=psatheesh@marvell.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).