netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Saeed Mahameed <saeedm@mellanox.com>
Subject: [pull request][net-next 0/6] Mellanox, mlx5 updates 2019-11-22
Date: Fri, 22 Nov 2019 21:26:47 +0000	[thread overview]
Message-ID: <20191122212541.17715-1-saeedm@mellanox.com> (raw)

Hi Dave,

This small series adds misc updates to mlx5 driver.

For more information please see tag log below.

Please pull and let me know if there is any problem.

Thanks,
Saeed.

---
The following changes since commit 3243e04ab1c06e7cb1402aff609c83de97956489:

  net: dsa: ocelot: fix "should it be static?" warnings (2019-11-22 10:09:10 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-updates-2019-11-22

for you to fetch changes up to 90ac245814abc30d2423474310654d31e3908b2f:

  net/mlx5e: Remove redundant pointer check (2019-11-22 13:18:20 -0800)

----------------------------------------------------------------
mlx5-updates-2019-11-22

1) Misc Cleanups
2) Software steering support for Geneve

----------------------------------------------------------------
Eli Cohen (1):
      net/mlx5e: Remove redundant pointer check

Leon Romanovsky (1):
      net/mlx5: Don't write read-only fields in MODIFY_HCA_VPORT_CONTEXT command

Saeed Mahameed (1):
      net/mlx5e: TC, Stub out ipv6 tun create header function

Yevgeny Kliteynik (3):
      net/mlx5: DR, Refactor VXLAN GPE flex parser tunnel code for SW steering
      net/mlx5: DR, Add HW bits and definitions for Geneve flex parser
      net/mlx5: DR, Add support for Geneve packets SW steering

 .../net/ethernet/mellanox/mlx5/core/en/tc_tun.c    |  26 ++---
 .../net/ethernet/mellanox/mlx5/core/en/tc_tun.h    |   7 ++
 .../mellanox/mlx5/core/steering/dr_matcher.c       |  60 ++++++++--
 .../ethernet/mellanox/mlx5/core/steering/dr_ste.c  | 126 ++++++++++++++-------
 .../mellanox/mlx5/core/steering/dr_types.h         |   9 +-
 .../mellanox/mlx5/core/steering/mlx5_ifc_dr.h      |  24 ++++
 drivers/net/ethernet/mellanox/mlx5/core/vport.c    |  27 ++---
 include/linux/mlx5/mlx5_ifc.h                      |   1 +
 8 files changed, 187 insertions(+), 93 deletions(-)

             reply	other threads:[~2019-11-22 21:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 21:26 Saeed Mahameed [this message]
2019-11-22 21:26 ` [net-next 1/6] net/mlx5: Don't write read-only fields in MODIFY_HCA_VPORT_CONTEXT command Saeed Mahameed
2019-11-22 21:26 ` [net-next 2/6] net/mlx5: DR, Refactor VXLAN GPE flex parser tunnel code for SW steering Saeed Mahameed
2019-11-22 21:26 ` [net-next 3/6] net/mlx5: DR, Add HW bits and definitions for Geneve flex parser Saeed Mahameed
2019-11-22 21:26 ` [net-next 4/6] net/mlx5: DR, Add support for Geneve packets SW steering Saeed Mahameed
2019-11-22 21:26 ` [net-next 5/6] net/mlx5e: TC, Stub out ipv6 tun create header function Saeed Mahameed
2019-11-22 21:26 ` [net-next 6/6] net/mlx5e: Remove redundant pointer check Saeed Mahameed
2019-11-24  0:42 ` [pull request][net-next 0/6] Mellanox, mlx5 updates 2019-11-22 Jakub Kicinski

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=20191122212541.17715-1-saeedm@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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).