From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw108772 [PATCH] [v2] maintainers: add explicit maintainer for some bbdev PMDs
Date: Thu, 17 Mar 2022 17:48:37 -0400 (EDT) [thread overview]
Message-ID: <20220317214837.55B85314F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/108772
_apply patch failure_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Thursday, March 17 2022 21:45:53
Applied on: CommitID:80c5b4d6355d1dbece8dd1f812d374f3e24086bc
Apply patch set 108772 failed:
Checking patch MAINTAINERS...
error: while searching for:
T: git://dpdk.org/next/dpdk-next-crypto
F: lib/bbdev/
F: doc/guides/prog_guide/bbdev.rst
F: drivers/baseband/
F: drivers/baseband/turbo_sw/
F: drivers/baseband/fpga_lte_fec/
F: drivers/baseband/fpga_5gnr_fec/
F: drivers/baseband/acc100/
F: doc/guides/bbdevs/
F: app/test-bbdev/
F: doc/guides/tools/testbbdev.rst
F: examples/bbdev_app/
error: patch failed: MAINTAINERS:421
Hunk #2 succeeded at 1299 (offset 1 line).
Applying patch MAINTAINERS with 1 reject...
Rejected hunk #1.
Hunk #2 applied cleanly.
diff a/MAINTAINERS b/MAINTAINERS (rejected hunks)
@@ -421,12 +421,7 @@ M: Nicolas Chautru <nicolas.chautru@intel.com>
T: git://dpdk.org/next/dpdk-next-crypto
F: lib/bbdev/
F: doc/guides/prog_guide/bbdev.rst
-F: drivers/baseband/
-F: drivers/baseband/turbo_sw/
-F: drivers/baseband/fpga_lte_fec/
-F: drivers/baseband/fpga_5gnr_fec/
-F: drivers/baseband/acc100/
-F: doc/guides/bbdevs/
+F: doc/guides/bbdevs/features/default.ini
F: app/test-bbdev/
F: doc/guides/tools/testbbdev.rst
F: examples/bbdev_app/
https://lab.dpdk.org/results/dashboard/patchsets/21517/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-03-17 21: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=20220317214837.55B85314F@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).