From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw127814 [PATCH] net/gve: fix bug in verify driver compatibility
Date: Sun, 11 Jun 2023 10:44:26 -0700 (PDT) [thread overview]
Message-ID: <648607fa.170a0220.d95e8.9097SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/127814
_apply patch failure_
Submitter: Rushil Gupta <rushilg@google.com>
Date: Thursday, June 01 2023 03:15:13
Applied on: CommitID:c9df59bcc9bec67783de98486879594e52bdc418
Apply patch set 127814 failed:
Checking patch drivers/net/gve/gve_ethdev.c...
error: while searching for:
(char *)driver_info->os_version_str2);
err = gve_adminq_verify_driver_compatibility(priv,
sizeof(struct gve_driver_info), (dma_addr_t)driver_info);
/* It's ok if the device doesn't support this */
if (err == -EOPNOTSUPP)
err = 0;
error: patch failed: drivers/net/gve/gve_ethdev.c:276
Applying patch drivers/net/gve/gve_ethdev.c with 1 reject...
Rejected hunk #1.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/drivers/net/gve/gve_ethdev.c b/drivers/net/gve/gve_ethdev.c (rejected hunks)
@@ -276,7 +276,8 @@ gve_verify_driver_compatibility(struct gve_priv *priv)
(char *)driver_info->os_version_str2);
err = gve_adminq_verify_driver_compatibility(priv,
- sizeof(struct gve_driver_info), (dma_addr_t)driver_info);
+ sizeof(struct gve_driver_info),
+ (dma_addr_t)driver_info_mem->iova);
/* It's ok if the device doesn't support this */
if (err == -EOPNOTSUPP)
err = 0;
https://lab.dpdk.org/results/dashboard/patchsets/26479/
UNH-IOL DPDK Community Lab
next reply other threads:[~2023-06-11 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 17:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-11 18:13 dpdklab
2023-06-11 17:58 dpdklab
2023-06-10 19:04 dpdklab
2023-06-09 22:41 dpdklab
2023-06-01 3:30 dpdklab
[not found] <20230601031513.453016-1-rushilg@google.com>
2023-06-01 3:17 ` 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=648607fa.170a0220.d95e8.9097SMTPIN_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).