DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Raslan Darawsheh <rasland@mellanox.com>,
	Ori Kam <orika@mellanox.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix ConnectX-4LX Tx burst routines set
Date: Mon, 6 Jan 2020 14:52:35 +0000	[thread overview]
Message-ID: <AM0PR0502MB40192EC163E38D0D23B408CDD23C0@AM0PR0502MB4019.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1576838905-26817-1-git-send-email-viacheslavo@mellanox.com>



From: Viacheslav Ovsiienko
> The tx_burst routine supporting multi-segment packets with legacy MPW
> and without inline was missed, and there was no valid selection for these
> options, patch adds the missing routine.
> 
> Fixes: 82e75f8323bf ("net/mlx5: fix legacy multi-packet Tx descriptors")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Acked-by: Matan Azrad <matan@mellanox.com>

  reply	other threads:[~2020-01-06 14:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 10:48 Viacheslav Ovsiienko
2020-01-06 14:52 ` Matan Azrad [this message]
2020-01-08  8:51 ` Raslan Darawsheh
2020-01-08 14:53 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2020-01-08 14:54   ` Ferruh Yigit
2020-01-08 15:50     ` Slava Ovsiienko
2020-01-08 15:54       ` Ferruh Yigit
2020-01-09  9:03         ` Slava Ovsiienko
2020-01-09 10:50           ` Ferruh Yigit
2020-01-09 11:10             ` Slava Ovsiienko
2020-01-09 14:27               ` Raslan Darawsheh
2020-01-09 11:07 ` [dpdk-dev] [PATCH v2] " Viacheslav Ovsiienko

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=AM0PR0502MB40192EC163E38D0D23B408CDD23C0@AM0PR0502MB4019.eurprd05.prod.outlook.com \
    --to=matan@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@mellanox.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).