From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw96494 [PATCH] doc: announce SA config option struct changes
Date: Sat, 31 Jul 2021 14:13:07 -0400 (EDT) [thread overview]
Message-ID: <20210731181307.481FC446@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/96494
_apply patch failure_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Saturday, July 31 2021 17:44:28
Applied on: CommitID:23ce9e0a193636e2f5ec9b386ddd5307c17e9723
Apply patch set 96494 failed:
Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
* security: The functions ``rte_security_set_pkt_metadata`` and
``rte_security_get_userdata`` will be made inline functions and additional
flags will be added in structure ``rte_security_ctx`` in DPDK 21.11.
error: patch failed: doc/guides/rel_notes/deprecation.rst:151
Applying patch doc/guides/rel_notes/deprecation.rst with 1 reject...
Rejected hunk #1.
diff a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst (rejected hunks)
@@ -151,3 +151,7 @@ Deprecation Notices
* security: The functions ``rte_security_set_pkt_metadata`` and
``rte_security_get_userdata`` will be made inline functions and additional
flags will be added in structure ``rte_security_ctx`` in DPDK 21.11.
+
+* security: The IPsec SA config options ``struct rte_security_ipsec_sa_options``
+ will be updated with new fields to support new features like IPsec inner
+ checksum, tunnel header verification, TSO in case of protocol offload.
https://lab.dpdk.org/results/dashboard/patchsets/18064/
UNH-IOL DPDK Community Lab
reply other threads:[~2021-07-31 18:13 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=20210731181307.481FC446@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).