patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Matan Azrad <matan@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	Yongseok Koh <yskoh@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] doc: update features supported by mlx
Date: Wed, 31 Jul 2019 00:21:18 +0200	[thread overview]
Message-ID: <30098069.a80XJoDPsI@xps> (raw)
In-Reply-To: <AM0PR0502MB4019AB220E87494F1F2D2369D2DC0@AM0PR0502MB4019.eurprd05.prod.outlook.com>

30/07/2019 18:32, Matan Azrad:
> From: Thomas Monjalon
> > Flow control was not documented as a supported feature since the first fill of
> > features matrix for mlx drivers.
> > 
> > Flow API and CRC offload flag support in mlx4 were missing in the feature
> > matrix when they were implemented (see below commits).
> > 
> > Fixes: 46d5736a7049 ("net/mlx4: support basic flow items and actions")
> > Fixes: ce07b1514d59 ("net/mlx4: fix CRC stripping capability report")
> > Fixes: e86b85ca757b ("doc: fill nics features matrix for mlx")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> 
> Acked-by: Matan Azrad <matan@mellanox.com>

Applied




      reply	other threads:[~2019-07-30 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 15:06 [dpdk-stable] " Thomas Monjalon
2019-07-30 16:32 ` Matan Azrad
2019-07-30 22:21   ` Thomas Monjalon [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=30098069.a80XJoDPsI@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=matan@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@mellanox.com \
    --cc=yskoh@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).