From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Edward Srouji <edwards@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: [PATCH rdma-next 0/4] Add XRQ and SRQ support to DEVX interface
Date: Thu, 8 Aug 2019 11:43:54 +0300 [thread overview]
Message-ID: <20190808084358.29517-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Hi,
This small series extends DEVX interface with SRQ and XRQ legacy commands.
Thanks
Yishai Hadas (4):
net/mlx5: Use debug message instead of warn
net/mlx5: Add XRQ legacy commands opcodes
IB/mlx5: Add legacy events to DEVX list
IB/mlx5: Expose XRQ legacy commands over the DEVX interface
drivers/infiniband/hw/mlx5/devx.c | 12 ++++++++++++
drivers/net/ethernet/mellanox/mlx5/core/cmd.c | 4 ++++
drivers/net/ethernet/mellanox/mlx5/core/qp.c | 2 +-
include/linux/mlx5/device.h | 9 +++++++++
include/linux/mlx5/mlx5_ifc.h | 2 ++
5 files changed, 28 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2019-08-08 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 8:43 Leon Romanovsky [this message]
2019-08-08 8:43 ` [PATCH mlx5-next 1/4] net/mlx5: Use debug message instead of warn Leon Romanovsky
2019-08-08 8:43 ` [PATCH mlx5-next 2/4] net/mlx5: Add XRQ legacy commands opcodes Leon Romanovsky
2019-08-08 8:43 ` [PATCH mlx5-next 3/4] IB/mlx5: Add legacy events to DEVX list Leon Romanovsky
2019-08-08 8:43 ` [PATCH rdma-next 4/4] IB/mlx5: Expose XRQ legacy commands over the DEVX interface Leon Romanovsky
2019-08-08 10:11 ` [PATCH rdma-next 0/4] Add XRQ and SRQ support to " Leon Romanovsky
2019-08-12 15:43 ` Doug Ledford
2019-08-13 10:06 ` Leon Romanovsky
2019-08-13 16:28 ` Doug Ledford
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=20190808084358.29517-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=edwards@mellanox.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yishaih@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).