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| pw106453 [PATCH] common/cnxk: fix base rule merging only for ingress
Date: Mon, 24 Jan 2022 23:48:59 -0500 (EST)	[thread overview]
Message-ID: <20220125044859.8271213C6@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Satheesh Paul <psatheesh@marvell.com>
Date: Tuesday, January 25 2022 04:17:59 
Applied on: CommitID:8a5a91401dc23ddab1ddea3667a17a615a25077f
Apply patch set 106453 failed:

Checking patch drivers/common/cnxk/roc_npc_mcam.c...
error: while searching for:
	if (pst->set_ipv6ext_ltype_mask)
		npc_set_ipv6ext_ltype_mask(pst);

	if (pst->is_vf) {
		(void)mbox_alloc_msg_npc_read_base_steer_rule(npc->mbox);
		rc = mbox_process_msg(npc->mbox, (void *)&base_rule_rsp);
		if (rc) {

error: patch failed: drivers/common/cnxk/roc_npc_mcam.c:752
Applying patch drivers/common/cnxk/roc_npc_mcam.c with 1 reject...
Rejected hunk #1.
diff a/drivers/common/cnxk/roc_npc_mcam.c b/drivers/common/cnxk/roc_npc_mcam.c	(rejected hunks)
@@ -752,7 +752,7 @@ npc_program_mcam(struct npc *npc, struct npc_parse_state *pst, bool mcam_alloc)
 	if (pst->set_ipv6ext_ltype_mask)
 		npc_set_ipv6ext_ltype_mask(pst);
 
-	if (pst->is_vf) {
+	if (pst->is_vf && pst->flow->nix_intf == NIX_INTF_RX) {
 		(void)mbox_alloc_msg_npc_read_base_steer_rule(npc->mbox);
 		rc = mbox_process_msg(npc->mbox, (void *)&base_rule_rsp);
 		if (rc) {

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2022-01-25  4:49 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=20220125044859.8271213C6@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).