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| pw136534 [PATCH] net/netvsc: fix parsing of VLAN metadata
Date: Thu, 08 Feb 2024 06:32:52 -0800 (PST)	[thread overview]
Message-ID: <65c4e614.620a0220.b447f.d51dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_apply patch failure_

Submitter: Alan Elder <alan.elder@microsoft.com>
Date: Thursday, February 08 2024 14:12:38 
Applied on: CommitID:805c5507267b6ef7a0cdcfc33aa326bc1de8c80b
Apply patch set 136534 failed:

Cloning the DPDK mirror at: https://github.com/DPDK/dpdk.git (Attempt 1 of 3)
Trying to checkout branch: main
Checked out to main (a4ce111cc89f580b8c4aad51bdb061acbdfde86b)
Done: main commit a4ce111cc89f580b8c4aad51bdb061acbdfde86b
Trying to checkout branch: origin/next-net-for-main
Checked out to next-net-for-main (805c5507267b6ef7a0cdcfc33aa326bc1de8c80b)
Applying patch...

Failed to apply patch:
Applying: net/netvsc: fix parsing of VLAN metadata
error: patch failed: .mailmap:32
error: .mailmap: patch does not apply
error: patch failed: drivers/net/netvsc/hn_rxtx.c:42
error: drivers/net/netvsc/hn_rxtx.c: patch does not apply
error: patch failed: drivers/net/netvsc/ndis.h:316
error: drivers/net/netvsc/ndis.h: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
hint: Use 'git am --show-current-patch' to see the failed patch
Using index info to reconstruct a base tree...
M	.mailmap
M	drivers/net/netvsc/hn_rxtx.c
Patch failed at 0001 net/netvsc: fix parsing of VLAN metadata
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: main
Checked out to main (805c5507267b6ef7a0cdcfc33aa326bc1de8c80b)
Applying patch...

Failed to apply patch:
Applying: net/netvsc: fix parsing of VLAN metadata
error: patch failed: .mailmap:32
error: .mailmap: patch does not apply
error: patch failed: drivers/net/netvsc/hn_rxtx.c:42
error: drivers/net/netvsc/hn_rxtx.c: patch does not apply
error: patch failed: drivers/net/netvsc/ndis.h:316
error: drivers/net/netvsc/ndis.h: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
hint: Use 'git am --show-current-patch' to see the failed patch
Using index info to reconstruct a base tree...
M	.mailmap
M	drivers/net/netvsc/hn_rxtx.c
Patch failed at 0001 net/netvsc: fix parsing of VLAN metadata
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/29094/

UNH-IOL DPDK Community Lab

             reply	other threads:[~2024-02-08 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 14:32 dpdklab [this message]
     [not found] <PA4PR83MB0526398D23186AB50C38D0EF97442@PA4PR83MB0526.EURPRD83.prod.outlook.com>
2024-02-08 13:51 ` qemudev
2024-02-08 14:16 ` 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=65c4e614.620a0220.b447f.d51dSMTPIN_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).