From: Saeed Mahameed <saeedm@mellanox.com>
To: Saeed Mahameed <saeedm@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: [PATCH mlx5-next 0/6] Mellanox, mlx5-next minor updates 2019-05-29
Date: Wed, 29 May 2019 22:50:20 +0000 [thread overview]
Message-ID: <20190529224949.18194-1-saeedm@mellanox.com> (raw)
Hi All,
This series provides some low level updates for mlx5 driver needed for
both rdma and netdev trees.
Eli adds termination flow steering table bits and hardware definitions.
Moshe introduces the core dump HW access registers definitions.
Parav refactors and cleans-up VF representors functions handlers.
Vu renames host_params bits to function_changed bits and add the
support for eswitch functions change event in the eswitch general case.
(for both legacy and switchdev modes).
In case of no objection this series will be applied to mlx5-next branch.
Thanks,
Saeed.
Eli Britstein (1):
net/mlx5: Introduce termination table bits
Moshe Shemesh (1):
net/mlx5: Add core dump register access HW bits
Parav Pandit (2):
{IB,net}/mlx5: No need to typecast from void* to mlx5_ib_dev*
{IB,net}/mlx5: Constify rep ops functions pointers
Vu Pham (2):
net/mlx5: E-Switch, Replace host_params event with functions_changed
event
net/mlx5: E-Switch, Honor eswitch functions changed event cap
drivers/infiniband/hw/mlx5/ib_rep.c | 19 ++--
drivers/infiniband/hw/mlx5/ib_rep.h | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/cmd.c | 4 +-
.../net/ethernet/mellanox/mlx5/core/ecpf.c | 27 -----
.../net/ethernet/mellanox/mlx5/core/ecpf.h | 4 -
.../net/ethernet/mellanox/mlx5/core/en_rep.c | 15 +--
.../net/ethernet/mellanox/mlx5/core/en_rep.h | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/eq.c | 5 +-
.../net/ethernet/mellanox/mlx5/core/eswitch.c | 32 +++++-
.../net/ethernet/mellanox/mlx5/core/eswitch.h | 20 +++-
.../mellanox/mlx5/core/eswitch_offloads.c | 107 ++++++++++--------
.../net/ethernet/mellanox/mlx5/core/events.c | 4 +-
.../net/ethernet/mellanox/mlx5/core/fs_cmd.c | 3 +
include/linux/mlx5/device.h | 2 +-
include/linux/mlx5/driver.h | 1 +
include/linux/mlx5/eswitch.h | 20 ++--
include/linux/mlx5/fs.h | 1 +
include/linux/mlx5/mlx5_ifc.h | 33 ++++--
18 files changed, 177 insertions(+), 124 deletions(-)
--
2.21.0
next reply other threads:[~2019-05-29 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 22:50 Saeed Mahameed [this message]
2019-05-29 22:50 ` [PATCH mlx5-next 1/6] net/mlx5: Add core dump register access HW bits Saeed Mahameed
2019-05-29 22:50 ` [PATCH mlx5-next 2/6] net/mlx5: Introduce termination table bits Saeed Mahameed
2019-05-29 22:50 ` [PATCH mlx5-next 3/6] net/mlx5: E-Switch, Replace host_params event with functions_changed event Saeed Mahameed
2019-05-29 22:50 ` [PATCH mlx5-next 4/6] net/mlx5: E-Switch, Honor eswitch functions changed event cap Saeed Mahameed
2019-05-29 22:50 ` [PATCH mlx5-next 5/6] {IB,net}/mlx5: No need to typecast from void* to mlx5_ib_dev* Saeed Mahameed
2019-05-29 22:50 ` [PATCH mlx5-next 6/6] {IB,net}/mlx5: Constify rep ops functions pointers Saeed Mahameed
2019-05-31 19:29 ` [PATCH mlx5-next 0/6] Mellanox, mlx5-next minor updates 2019-05-29 Saeed Mahameed
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=20190529224949.18194-1-saeedm@mellanox.com \
--to=saeedm@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--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