From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw132737 [PATCH] ethdev: fix flow action async query coverity
Date: Tue, 17 Oct 2023 11:39:29 -0700 (PDT) [thread overview]
Message-ID: <652ed4e1.170a0220.16f4b.4d51SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/132737
_apply patch failure_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Tuesday, October 17 2023 08:23:17
Applied on: CommitID:99dcd1664982fd93d49ca159a97ad16537a1914f
Apply patch set 132737 failed:
Checking patch lib/ethdev/rte_flow.c...
error: while searching for:
const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
int ret;
ret = ops->async_action_handle_query(dev, queue_id, op_attr,
action_handle, data, user_data, error);
ret = flow_err(port_id, ret, error);
error: patch failed: lib/ethdev/rte_flow.c:2226
Applying patch lib/ethdev/rte_flow.c with 1 reject...
Rejected hunk #1.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/lib/ethdev/rte_flow.c b/lib/ethdev/rte_flow.c (rejected hunks)
@@ -2226,6 +2226,8 @@ rte_flow_async_action_handle_query(uint16_t port_id,
const struct rte_flow_ops *ops = rte_flow_ops_get(port_id, error);
int ret;
+ if (unlikely(!ops))
+ return -rte_errno;
ret = ops->async_action_handle_query(dev, queue_id, op_attr,
action_handle, data, user_data, error);
ret = flow_err(port_id, ret, error);
https://lab.dpdk.org/results/dashboard/patchsets/27962/
UNH-IOL DPDK Community Lab
next reply other threads:[~2023-10-17 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 18:39 dpdklab [this message]
[not found] <20231017082317.735106-1-suanmingm@nvidia.com>
2023-10-17 8:25 ` checkpatch
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=652ed4e1.170a0220.16f4b.4d51SMTPIN_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).