From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH rdma-next 0/2] Small fix and code refactoring for mlx5
Date: Fri, 17 Jun 2016 15:33:30 +0300 [thread overview]
Message-ID: <1466166812-730-1-git-send-email-leon@kernel.org> (raw)
Hi Doug,
These two patches are intended for rdna-next and related
to mlx5 only.
Despite the fact that these patches were tested and found
that no merge conflict is expected between IB and net parts
of mlx5 driver, we would like to ask you to take into your
tree this refactored code.
Such move will give us enough time to respond in case other
developers (non-Mellanox) will send patches in that area and
will cause to merge conflicts during Linus's merge window.
Thanks
Artemy Kovalyov (2):
IB/mlx5: Fix MODIFY_QP command input structure
{net, IB}/mlx5: Refactor internal SRQ API
drivers/infiniband/hw/mlx5/srq.c | 102 ++++------
drivers/net/ethernet/mellanox/mlx5/core/srq.c | 265 ++++++++++++++------------
include/linux/mlx5/driver.h | 6 +-
include/linux/mlx5/qp.h | 5 +-
include/linux/mlx5/srq.h | 25 +++
5 files changed, 218 insertions(+), 185 deletions(-)
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-06-17 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 12:33 Leon Romanovsky [this message]
[not found] ` <1466166812-730-1-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-06-17 12:33 ` [PATCH rdma-next 1/2] IB/mlx5: Fix MODIFY_QP command input structure Leon Romanovsky
2016-06-17 12:33 ` [PATCH rdma-next 2/2] {net, IB}/mlx5: Refactor internal SRQ API Leon Romanovsky
2016-06-23 15:21 ` [PATCH rdma-next 0/2] Small fix and code refactoring for mlx5 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=1466166812-730-1-git-send-email-leon@kernel.org \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.