From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, dev@dpdk.org
Cc: stable@dpdk.org, Sunil Kulkarni <sunil.kulkarni@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] net/thunderx: fix multi segment xmit function return
Date: Mon, 4 Dec 2017 15:59:25 -0800 [thread overview]
Message-ID: <cea52584-4f81-2740-b73e-2c53ecfaf58d@intel.com> (raw)
In-Reply-To: <20171128132238.15592-1-jerin.jacob@caviumnetworks.com>
On 11/28/2017 5:22 AM, Jerin Jacob wrote:
> multi segment version of tx burst function was not
> returning the actual number of packets sent out
> in PMD xmit function.
>
> Fixes: 1c421f18e0 ("net/thunderx: add single and multi-segment Tx")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Signed-off-by: Sunil Kulkarni <sunil.kulkarni@caviumnetworks.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-12-04 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 13:22 Jerin Jacob
2017-12-04 23:59 ` 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=cea52584-4f81-2740-b73e-2c53ecfaf58d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=stable@dpdk.org \
--cc=sunil.kulkarni@caviumnetworks.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).