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: |WARNING| pw117239 [PATCH] [v1] doc: update to include bbdev snippet using literalinclude
Date: Fri, 30 Sep 2022 21:34:22 -0400 (EDT)	[thread overview]
Message-ID: <20221001013422.05C126D509@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Saturday, October 01 2022 01:15:47 
Applied on: CommitID:8ae946970ed36f6f8795ea056350a500007c91d8
Apply patch set 117239 failed:

Checking patch doc/guides/prog_guide/bbdev.rst...
error: while searching for:
The API allows more generally for flexibility in what the PMD may support (capability flags) and
flexibility to adjust some of the parameters of the processing.

The operation/capability flags that can be set for each FFT operation are given below.

  **NOTE:** The actual operation flags that may be used with a specific
  BBDEV PMD are dependent on the driver capabilities as reported via
  ``rte_bbdev_info_get()``, and may be a subset of those below.

+--------------------------------------------------------------------+
|Description of FFT capability flags                                 |
+====================================================================+

error: patch failed: doc/guides/prog_guide/bbdev.rst:1135
Checking patch lib/bbdev/rte_bbdev_op.h...
Hunk #1 succeeded at 374 (offset -28 lines).
Hunk #2 succeeded at 419 (offset -28 lines).
Hunk #3 succeeded at 450 (offset -28 lines).
Hunk #4 succeeded at 512 (offset -28 lines).
Hunk #5 succeeded at 621 (offset -28 lines).
Hunk #6 succeeded at 642 (offset -28 lines).
Hunk #7 succeeded at 657 (offset -28 lines).
error: while searching for:
		struct rte_bbdev_op_enc_ldpc_tb_params tb_params;
	};
};

/** Operation structure for FFT processing.
 *

error: patch failed: lib/bbdev/rte_bbdev_op.h:716
error: while searching for:
 * The output mbuf data structure is expected to be allocated by the
 * application with enough room for the output data.
 */
struct rte_bbdev_op_fft {
	/** Input data starting from first antenna */
	struct rte_bbdev_op_data base_input;

error: patch failed: lib/bbdev/rte_bbdev_op.h:725
error: while searching for:
	/** Adjust the FP6 exponent for INT<->FP16 conversion */
	uint16_t fp16_exp_adjust;
};

/** List of the capabilities for the Turbo Decoder */
struct rte_bbdev_op_cap_turbo_dec {

error: patch failed: lib/bbdev/rte_bbdev_op.h:765
Applying patch doc/guides/prog_guide/bbdev.rst with 1 reject...
Hunk #1 applied cleanly.
Hunk #2 applied cleanly.
Hunk #3 applied cleanly.
Hunk #4 applied cleanly.
Rejected hunk #5.
Applying patch lib/bbdev/rte_bbdev_op.h with 3 rejects...
Hunk #1 applied cleanly.
Hunk #2 applied cleanly.
Hunk #3 applied cleanly.
Hunk #4 applied cleanly.
Hunk #5 applied cleanly.
Hunk #6 applied cleanly.
Hunk #7 applied cleanly.
Rejected hunk #8.
Rejected hunk #9.
Rejected hunk #10.
diff a/doc/guides/prog_guide/bbdev.rst b/doc/guides/prog_guide/bbdev.rst	(rejected hunks)
@@ -1135,12 +1070,18 @@ A flexible number of Rx antennas are being processed in parallel with the same c
 The API allows more generally for flexibility in what the PMD may support (capability flags) and
 flexibility to adjust some of the parameters of the processing.
 
-The operation/capability flags that can be set for each FFT operation are given below.
+The structure passed for each FFT operation is given below,
+with the operation flags forming a bitmask in the ``op_flags`` field.
 
   **NOTE:** The actual operation flags that may be used with a specific
   BBDEV PMD are dependent on the driver capabilities as reported via
   ``rte_bbdev_info_get()``, and may be a subset of those below.
 
+.. literalinclude:: ../../../lib/bbdev/rte_bbdev_op.h
+   :language: c
+   :start-after: Structure rte_bbdev_op_fft 8<
+   :end-before: >8 End of structure rte_bbdev_op_fft.
+
 +--------------------------------------------------------------------+
 |Description of FFT capability flags                                 |
 +====================================================================+
diff a/lib/bbdev/rte_bbdev_op.h b/lib/bbdev/rte_bbdev_op.h	(rejected hunks)
@@ -716,6 +727,7 @@ struct rte_bbdev_op_ldpc_enc {
 		struct rte_bbdev_op_enc_ldpc_tb_params tb_params;
 	};
 };
+/* >8 End of structure rte_bbdev_op_ldpc_enc. */
 
 /** Operation structure for FFT processing.
  *
@@ -725,6 +737,8 @@ struct rte_bbdev_op_ldpc_enc {
  * The output mbuf data structure is expected to be allocated by the
  * application with enough room for the output data.
  */
+
+/* Structure rte_bbdev_op_fft 8< */
 struct rte_bbdev_op_fft {
 	/** Input data starting from first antenna */
 	struct rte_bbdev_op_data base_input;
@@ -765,6 +779,7 @@ struct rte_bbdev_op_fft {
 	/** Adjust the FP6 exponent for INT<->FP16 conversion */
 	uint16_t fp16_exp_adjust;
 };
+/* >8 End of structure rte_bbdev_op_fft. */
 
 /** List of the capabilities for the Turbo Decoder */
 struct rte_bbdev_op_cap_turbo_dec {

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2022-10-01  1:34 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=20221001013422.05C126D509@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).