From: Stephen Hemminger <stephen@networkplumber.org>
To: Francesco Mancino <francesco.mancino@tutus.se>
Cc: dev@dpdk.org
Subject: Re: [PATCH v5] net/tap: Allow jumbo frames
Date: Mon, 8 Aug 2022 07:43:18 -0700 [thread overview]
Message-ID: <20220808074318.1089accf@hermes.local> (raw)
In-Reply-To: <bcf64f0d-8afb-af19-7c0a-e7314f55f1a0@tutus.se>
On Mon, 8 Aug 2022 14:29:25 +0200
Francesco Mancino <francesco.mancino@tutus.se> wrote:
> eth_dev_validate_mtu, introduced in 990912e676e, validates configured
> MTU plus overhead against max_rx_pktlen.
> Since TAP is a virtual device, it should support as big MTU as possible.
In all your tries at the patch, you must not have run checkpatch because
it would have informed you that Signed-off-by (a.k.a Developers Certificate of Origin)
is required for any DPDK patch to be accepted.
Please add Signed-off-by and fix the cast.
prev parent reply other threads:[~2022-08-08 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 12:29 Francesco Mancino
2022-08-08 14:43 ` Stephen Hemminger [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=20220808074318.1089accf@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=francesco.mancino@tutus.se \
/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).