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| pw122433 [PATCH] [v1, 1/1] baseband/acc: fix check after deref and dead code
Date: Fri, 20 Jan 2023 16:08:12 -0500 (EST)	[thread overview]
Message-ID: <20230120210812.9F22545F@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Friday, January 20 2023 20:55:53 
Applied on: CommitID:2a211079a92e962bbd0ec81e425a6ffc32890e67
Apply patch set 122433 failed:

Checking patch drivers/baseband/acc/rte_acc100_pmd.c...
error: while searching for:
	int ret, cbm;
	struct rte_bbdev_enc_op *op;

	if (q == NULL)
		return 0;
#ifdef RTE_LIBRTE_BBDEV_DEBUG
	if (unlikely(ops == 0))
		return 0;
#endif
	op = acc_op_tail(q, 0);
	if (unlikely(ops == NULL || op == NULL))
		return 0;

error: patch failed: drivers/baseband/acc/rte_acc100_pmd.c:4106
Applying patch drivers/baseband/acc/rte_acc100_pmd.c with 1 reject...
Rejected hunk #1.
diff a/drivers/baseband/acc/rte_acc100_pmd.c b/drivers/baseband/acc/rte_acc100_pmd.c	(rejected hunks)
@@ -4106,12 +4106,9 @@ acc100_dequeue_ldpc_enc(struct rte_bbdev_queue_data *q_data,
 	int ret, cbm;
 	struct rte_bbdev_enc_op *op;
 
-	if (q == NULL)
-		return 0;
-#ifdef RTE_LIBRTE_BBDEV_DEBUG
-	if (unlikely(ops == 0))
+	if (avail == 0)
 		return 0;
-#endif
+
 	op = acc_op_tail(q, 0);
 	if (unlikely(ops == NULL || op == NULL))
 		return 0;

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2023-01-20 21:08 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=20230120210812.9F22545F@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).