From: Stephen Hemminger <stephen@networkplumber.org>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: Aman Singh <aman.deep.singh@intel.com>, <dev@dpdk.org>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH] app/testpmd: report minimum and maximum MTU
Date: Mon, 21 Jul 2025 20:56:57 -0700 [thread overview]
Message-ID: <20250721205657.4956306d@hermes.local> (raw)
In-Reply-To: <20250716102847.1118815-1-dsosnowski@nvidia.com>
On Wed, 16 Jul 2025 12:28:46 +0200
Dariusz Sosnowski <dsosnowski@nvidia.com> wrote:
> Add reporting of minimum and maximum allowed MTU on a given port
> to "show port info <id>" command.
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
Queued to next-net for 25.11
prev parent reply other threads:[~2025-07-22 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:28 Dariusz Sosnowski
2025-07-22 3:56 ` 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=20250721205657.4956306d@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=viacheslavo@nvidia.com \
/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).