From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw111005 [PATCH] [v4] net/nfp: make sure MTU is never larger than mbufsize
Date: Tue, 10 May 2022 21:28:41 -0400 (EDT) [thread overview]
Message-ID: <20220511012841.E7F374F8@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/111005
_apply patch failure_
Submitter: Peng Zhang <peng.zhang@corigine.com>
Date: Wednesday, May 11 2022 01:15:53
Applied on: CommitID:36db4a1ad46448a2610133b021677ce6a0e0534e
Apply patch set 111005 failed:
Checking patch drivers/net/nfp/nfp_common.c...
error: while searching for:
*/
dev_info->max_rx_pktlen = NFP_FRAME_SIZE_MAX;
dev_info->max_mtu = hw->max_mtu;
/* Next should change when PF support is implemented */
dev_info->max_mac_addrs = 1;
error: patch failed: drivers/net/nfp/nfp_common.c:702
Hunk #3 succeeded at 959 (offset -10 lines).
Applying patch drivers/net/nfp/nfp_common.c with 1 reject...
Hunk #1 applied cleanly.
Rejected hunk #2.
Hunk #3 applied cleanly.
diff a/drivers/net/nfp/nfp_common.c b/drivers/net/nfp/nfp_common.c (rejected hunks)
@@ -702,6 +709,7 @@ nfp_net_infos_get(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
*/
dev_info->max_rx_pktlen = NFP_FRAME_SIZE_MAX;
dev_info->max_mtu = hw->max_mtu;
+ dev_info->min_mtu = RTE_ETHER_MIN_MTU;
/* Next should change when PF support is implemented */
dev_info->max_mac_addrs = 1;
https://lab.dpdk.org/results/dashboard/patchsets/22066/
UNH-IOL DPDK Community Lab
reply other threads:[~2022-05-11 1:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220511012841.E7F374F8@noxus.dpdklab.iol.unh.edu \
--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).