From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw155009 [PATCH] net/bonding: avoid RSS reta update in flow-isolation mode
Date: Wed, 09 Jul 2025 13:06:09 -0700 (PDT) [thread overview]
Message-ID: <686ecbb1.050a0220.104fe.0067SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250704132207.5021-1-madhuker.mythri@oracle.com>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/155009
_apply patch failure_
Submitter: Madhuker Mythri <madhuker.mythri@oracle.com>
Date: Friday, July 04 2025 13:22:07
Applied on: CommitID:7e6d6106a4ef052d6a2a6bd6e83c5b16a36c65c9
Apply patch set 155009 failed:
Cloning the DPDK mirror at: https://github.com/DPDK/dpdk.git (Attempt 1 of 3)
Trying to checkout branch: origin/main
Checked out to main (7e6d6106a4ef052d6a2a6bd6e83c5b16a36c65c9)
Done: main commit 7e6d6106a4ef052d6a2a6bd6e83c5b16a36c65c9
Trying to checkout branch: origin/next-net-for-main
Checked out to next-net-for-main (ba982f9a1ca9b96ed0394b764f1523d482e963a2)
Applying patch...
Failed to apply patch:
Applying: net/bonding: avoid RSS reta update in flow-isolation mode
.git/rebase-apply/patch:15: trailing whitespace.
/*
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M drivers/net/bonding/rte_eth_bond_pmd.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/bonding/rte_eth_bond_pmd.c
CONFLICT (content): Merge conflict in drivers/net/bonding/rte_eth_bond_pmd.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 net/bonding: avoid RSS reta update in flow-isolation mode
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Trying to checkout branch: origin/main
Checked out to main (7e6d6106a4ef052d6a2a6bd6e83c5b16a36c65c9)
Applying patch...
Failed to apply patch:
Applying: net/bonding: avoid RSS reta update in flow-isolation mode
.git/rebase-apply/patch:15: trailing whitespace.
/*
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M drivers/net/bonding/rte_eth_bond_pmd.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/bonding/rte_eth_bond_pmd.c
CONFLICT (content): Merge conflict in drivers/net/bonding/rte_eth_bond_pmd.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 net/bonding: avoid RSS reta update in flow-isolation mode
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
https://lab.dpdk.org/results/dashboard/patchsets/33592/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2025-07-09 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250704132207.5021-1-madhuker.mythri@oracle.com>
2025-07-04 12:47 ` |SUCCESS| " qemudev
2025-07-04 12:52 ` qemudev
2025-07-04 13:22 ` |WARNING| " checkpatch
2025-07-04 14:43 ` |SUCCESS| " 0-day Robot
2025-07-09 15:54 ` |WARNING| " dpdklab
2025-07-09 16:53 ` dpdklab
2025-07-09 20:06 ` dpdklab [this message]
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=686ecbb1.050a0220.104fe.0067SMTPIN_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).