From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw132483 [PATCH] [v1, 1/1] doc: bbdev device discovery clarification
Date: Tue, 10 Oct 2023 14:50:33 -0700 (PDT) [thread overview]
Message-ID: <6525c729.0c0a0220.3a1d7.549bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/132483
_apply patch failure_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Tuesday, October 10 2023 20:34:10
Applied on: CommitID:fbafb3676c482dab60c0b5465b47f2ea33893a36
Apply patch set 132483 failed:
Checking patch doc/guides/prog_guide/bbdev.rst...
Checking patch lib/bbdev/rte_bbdev.h...
error: while searching for:
/** FFT windowing width for 2048 FFT - size defined in capability. */
uint16_t *fft_window_width;
};
/** Macro used at end of bbdev PMD list */
#define RTE_BBDEV_END_OF_CAPABILITIES_LIST() \
error: patch failed: lib/bbdev/rte_bbdev.h:352
Hunk #3 succeeded at 361 (offset -3 lines).
Hunk #4 succeeded at 371 (offset -3 lines).
Applied patch doc/guides/prog_guide/bbdev.rst cleanly.
Applying patch lib/bbdev/rte_bbdev.h with 1 reject...
Hunk #1 applied cleanly.
Rejected hunk #2.
Hunk #3 applied cleanly.
Hunk #4 applied cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/lib/bbdev/rte_bbdev.h b/lib/bbdev/rte_bbdev.h (rejected hunks)
@@ -352,6 +354,7 @@ struct rte_bbdev_driver_info {
/** FFT windowing width for 2048 FFT - size defined in capability. */
uint16_t *fft_window_width;
};
+/* >8 End of structure rte_bbdev_driver_info. */
/** Macro used at end of bbdev PMD list */
#define RTE_BBDEV_END_OF_CAPABILITIES_LIST() \
https://lab.dpdk.org/results/dashboard/patchsets/27890/
UNH-IOL DPDK Community Lab
next reply other threads:[~2023-10-10 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 21:50 dpdklab [this message]
[not found] <20231010203410.773132-2-nicolas.chautru@intel.com>
2023-10-10 20:14 ` |WARNING| pw132483 [PATCH v1 " qemudev
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=6525c729.0c0a0220.3a1d7.549bSMTPIN_ADDED_MISSING@mx.google.com \
--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).