From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw156163 [PATCH] net/netvsc: cache device parameters for hot plug events
Date: Wed, 10 Sep 2025 13:21:52 -0700 (PDT) [thread overview]
Message-ID: <68c1dde0.050a0220.2393b0.15a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1756170959-19822-1-git-send-email-longli@linuxonhyperv.com>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/156163
_apply patch failure_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Tuesday, August 26 2025 01:15:59
Applied on: CommitID:f41d2db45d8a23c3315929c190d098154732a1ce
Apply patch set 156163 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 (f41d2db45d8a23c3315929c190d098154732a1ce)
Done: main commit f41d2db45d8a23c3315929c190d098154732a1ce
Trying to checkout branch: origin/next-net-for-main
Checked out to next-net-for-main (96eebfe1330def4b2565fa09a299c2861d7d0d61)
Applying patch...
Failed to apply patch:
Applying: net/netvsc: cache device parameters for hot plug events
Using index info to reconstruct a base tree...
M drivers/net/netvsc/hn_ethdev.c
M drivers/net/netvsc/hn_var.h
M drivers/net/netvsc/hn_vf.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/netvsc/hn_ethdev.c
CONFLICT (content): Merge conflict in drivers/net/netvsc/hn_ethdev.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/netvsc: cache device parameters for hot plug events
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 (f41d2db45d8a23c3315929c190d098154732a1ce)
Applying patch...
Failed to apply patch:
Applying: net/netvsc: cache device parameters for hot plug events
Using index info to reconstruct a base tree...
M drivers/net/netvsc/hn_ethdev.c
M drivers/net/netvsc/hn_var.h
M drivers/net/netvsc/hn_vf.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/netvsc/hn_ethdev.c
CONFLICT (content): Merge conflict in drivers/net/netvsc/hn_ethdev.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/netvsc: cache device parameters for hot plug events
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/33953/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2025-09-10 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1756170959-19822-1-git-send-email-longli@linuxonhyperv.com>
2025-08-26 0:47 ` |SUCCESS| " qemudev
2025-08-26 0:51 ` qemudev
2025-08-26 1:14 ` |WARNING| " checkpatch
2025-08-26 2:04 ` |SUCCESS| " 0-day Robot
2025-09-10 20:21 ` 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=68c1dde0.050a0220.2393b0.15a9SMTPIN_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).