From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw108352 [PATCH] [v2] common/cnxk: support CNF95xx B0 variant
Date: Fri, 25 Feb 2022 05:48:56 -0500 (EST) [thread overview]
Message-ID: <20220225104856.172F46D4C2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/108352
_apply patch failure_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Friday, February 25 2022 10:34:10
Applied on: CommitID:ee05a93e1e6633d0fdec409faf09f12a2e05b991
Apply patch set 108352 failed:
Checking patch doc/guides/rel_notes/release_22_03.rst...
error: while searching for:
* Added queue based priority flow control support for CN9K & CN10K.
* Added support for IP reassembly for inline inbound IPsec packets.
* Added support for packet marking in traffic manager.
* **Added an API for private user data in asymmetric crypto session.**
error: patch failed: doc/guides/rel_notes/release_22_03.rst:135
Checking patch drivers/common/cnxk/roc_model.c...
Checking patch drivers/common/cnxk/roc_model.h...
Applying patch doc/guides/rel_notes/release_22_03.rst with 1 reject...
Rejected hunk #1.
Applied patch drivers/common/cnxk/roc_model.c cleanly.
Applied patch drivers/common/cnxk/roc_model.h cleanly.
diff a/doc/guides/rel_notes/release_22_03.rst b/doc/guides/rel_notes/release_22_03.rst (rejected hunks)
@@ -135,6 +135,7 @@ New Features
* Added queue based priority flow control support for CN9K & CN10K.
* Added support for IP reassembly for inline inbound IPsec packets.
* Added support for packet marking in traffic manager.
+ * Added support for CNF95xx B0 variant SoC.
* **Added an API for private user data in asymmetric crypto session.**
https://lab.dpdk.org/results/dashboard/patchsets/21278/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-02-25 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220225104856.172F46D4C2@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).