From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: 3chas3@gmail.com, nirranjan@chelsio.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/cxgbe: announce Tx multi segs offload
Date: Tue, 14 Jan 2020 18:22:44 +0000 [thread overview]
Message-ID: <07dc70af-ddbc-fb2f-b8d6-ff32c089f12b@intel.com> (raw)
In-Reply-To: <1578995002-1634-1-git-send-email-rahul.lakkireddy@chelsio.com>
On 1/14/2020 9:43 AM, Rahul Lakkireddy wrote:
> Multi-segs Tx is already supported by CXGBE PMD. So, add the missing
> DEV_TX_OFFLOAD_MULTI_SEGS flag to the list of supported Tx offload
> features.
>
> Fixes: 436125e64174 ("net/cxgbe: update to Rx/Tx offload API")
> Cc: stable@dpdk.org
>
> Reported-by: Chas Williams <3chas3@gmail.com>
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-01-14 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 9:43 Rahul Lakkireddy
2020-01-14 18:22 ` Ferruh Yigit [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=07dc70af-ddbc-fb2f-b8d6-ff32c089f12b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=3chas3@gmail.com \
--cc=dev@dpdk.org \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=stable@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).