From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Chengwen Feng <fengchengwen@huawei.com>,
thomas@monjalon.net, ferruh.yigit@amd.com
Cc: dev@dpdk.org, aman.deep.singh@intel.com, yuying.zhang@intel.com
Subject: Re: [PATCH] app/testpmd: remove jumbo offload related code
Date: Thu, 20 Oct 2022 10:21:40 +0300 [thread overview]
Message-ID: <f03338c4-031e-9e57-cc0c-39cdb6f3376f@oktetlabs.ru> (raw)
In-Reply-To: <20221017090550.4188-1-fengchengwen@huawei.com>
On 10/17/22 12:05, Chengwen Feng wrote:
> The jumbo offload was removed from patch [1], but testpmd still exist
> jumbo offload related code, this patch removes it, and also updates
> the rst file.
>
> [1] ethdev: remove jumbo offload flag
>
> Fixes: b563c1421282 ("ethdev: remove jumbo offload flag")
> Cc: stable@dpdk.org
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-10-20 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 9:05 Chengwen Feng
2022-10-20 7:21 ` Andrew Rybchenko [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=f03338c4-031e-9e57-cc0c-39cdb6f3376f@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
--cc=yuying.zhang@intel.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).