automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw99829 [PATCH] [v4] doc: remove event crypto metadata deprecation note
Date: Wed,  6 Oct 2021 02:29:14 +0000 (UTC)	[thread overview]
Message-ID: <20211006022914.84FDA61CE7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/99829

_apply patch failure_

Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Monday, September 27 2021 15:22:44 
Applied on: CommitID:2700326085033fd13339a8de31f58a95d1ee9c3f
Apply patch set 99829 failed:

Checking patch doc/guides/rel_notes/deprecation.rst...
error: while searching for:
  An 8-byte reserved field will be added to the structure ``rte_event_timer`` to
  support future extensions.

* eventdev: Reserved bytes of ``rte_event_crypto_request`` is a space holder
  for ``response_info``. Both should be decoupled for better clarity.
  New space for ``response_info`` can be made by changing
  ``rte_event_crypto_metadata`` type to structure from union.
  This change is targeted for DPDK 21.11.

* metrics: The function ``rte_metrics_init`` will have a non-void return
  in order to notify errors instead of calling ``rte_exit``.


error: patch failed: doc/guides/rel_notes/deprecation.rst:254
Checking patch lib/eventdev/rte_event_crypto_adapter.h...
Applying patch doc/guides/rel_notes/deprecation.rst with 1 reject...
Rejected hunk #1.
Applied patch lib/eventdev/rte_event_crypto_adapter.h cleanly.
diff a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst	(rejected hunks)
@@ -254,12 +254,6 @@ Deprecation Notices
   An 8-byte reserved field will be added to the structure ``rte_event_timer`` to
   support future extensions.
 
-* eventdev: Reserved bytes of ``rte_event_crypto_request`` is a space holder
-  for ``response_info``. Both should be decoupled for better clarity.
-  New space for ``response_info`` can be made by changing
-  ``rte_event_crypto_metadata`` type to structure from union.
-  This change is targeted for DPDK 21.11.
-
 * metrics: The function ``rte_metrics_init`` will have a non-void return
   in order to notify errors instead of calling ``rte_exit``.
 

https://lab.dpdk.org/results/dashboard/patchsets/18992/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-10-06  2:29 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=20211006022914.84FDA61CE7@dpdk-ubuntu.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).