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| pw153609-153615 [PATCH] [v3, 7/7] net/ena: upgrade driver version to 2.13.0
Date: Thu, 22 May 2025 08:12:13 -0700 (PDT)	[thread overview]
Message-ID: <682f3ecd.170a0220.2ead12.74dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250522133029.3575-1-shaibran@amazon.com>

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

_apply patch failure_

Submitter: Shai Brandes <shaibran@amazon.com>
Date: Thursday, May 22 2025 13:30:29 
Applied on: CommitID:117e86c4b96ed761e9a7ab766261208fe81bf5ca
Apply patch set 153609-153615 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 (117e86c4b96ed761e9a7ab766261208fe81bf5ca)
Done: main commit 117e86c4b96ed761e9a7ab766261208fe81bf5ca
Trying to checkout branch: origin/next-net-for-main
Checked out to next-net-for-main (a0ad790eb9fcef4b00366ae474132bee4bcdab75)
Applying patch...

Failed to apply patch:
Applying: net/ena/base: avoid recalculating desc per entry
Using index info to reconstruct a base tree...
M	drivers/net/ena/base/ena_eth_com.c
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.
Applying: net/ena/base: coding style changes
Using index info to reconstruct a base tree...
M	drivers/net/ena/base/ena_com.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/ena/base/ena_com.c
No changes -- Patch already applied.
Applying: net/ena: separate doorbell logic for Rx and Tx
Using index info to reconstruct a base tree...
M	drivers/net/ena/base/ena_eth_com.h
M	drivers/net/ena/ena_ethdev.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/ena/ena_ethdev.c
No changes -- Patch already applied.
Applying: net/ena: support fragment bypass mode
Using index info to reconstruct a base tree...
M	doc/guides/nics/ena.rst
M	doc/guides/rel_notes/release_25_07.rst
M	drivers/net/ena/base/ena_com.c
M	drivers/net/ena/base/ena_com.h
M	drivers/net/ena/base/ena_defs/ena_admin_defs.h
M	drivers/net/ena/ena_ethdev.c
M	drivers/net/ena/ena_ethdev.h
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/ena/ena_ethdev.h
Auto-merging drivers/net/ena/ena_ethdev.c
CONFLICT (content): Merge conflict in drivers/net/ena/ena_ethdev.c
Auto-merging doc/guides/rel_notes/release_25_07.rst
CONFLICT (content): Merge conflict in doc/guides/rel_notes/release_25_07.rst
Auto-merging doc/guides/nics/ena.rst
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 net/ena: support fragment bypass 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 (117e86c4b96ed761e9a7ab766261208fe81bf5ca)
Applying patch...

Failed to apply patch:
Applying: net/ena/base: avoid recalculating desc per entry
Applying: net/ena/base: coding style changes
Applying: net/ena: separate doorbell logic for Rx and Tx
Applying: net/ena: support fragment bypass mode
Using index info to reconstruct a base tree...
M	doc/guides/rel_notes/release_25_07.rst
Falling back to patching base and 3-way merge...
Auto-merging doc/guides/rel_notes/release_25_07.rst
CONFLICT (content): Merge conflict in doc/guides/rel_notes/release_25_07.rst
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 net/ena: support fragment bypass 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/33235/

UNH-IOL DPDK Community Lab

      parent reply	other threads:[~2025-05-22 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250522133029.3575-1-shaibran@amazon.com>
2025-05-22 13:32 ` |WARNING| pw153615 [PATCH v3 " checkpatch
2025-05-22 15:12 ` 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=682f3ecd.170a0220.2ead12.74dfSMTPIN_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).