From: Or Gerlitz <ogerlitz@mellanox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Roland Dreier <roland@kernel.org>,
Amir Vadai <amirv@mellanox.com>, Tal Alon <talal@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: [PATCH V1 net-next 0/3] bonding and mlx4 fixes for the HA/LAG support and mlx4 reset flow
Date: Sun, 8 Feb 2015 11:49:31 +0200 [thread overview]
Message-ID: <1423388974-9635-1-git-send-email-ogerlitz@mellanox.com> (raw)
Hi Dave,
There are two fixes to the boding + mlx4 HA/LAG support from Moni and a patch from Yishai
which does further hardening of the mlx4 reset support for IB kernel ULPs.
Or.
changes from V0:
- addressed feedback from Sergei Shtylyov and removed un-related tabbing change
Moni Shoua (2):
net/bonding: Fix potential bad memory access during bonding events
IB/mlx4: Always use the correct port for mirrored multicast attachments
Yishai Hadas (1):
IB/mlx4: Reset flow support for IB kernel ULPs
drivers/infiniband/hw/mlx4/cq.c | 57 +++++++++++++++++++++++++++
drivers/infiniband/hw/mlx4/main.c | 70 +++++++++++++++++++++++++++++++++-
drivers/infiniband/hw/mlx4/mlx4_ib.h | 9 ++++
drivers/infiniband/hw/mlx4/qp.c | 59 +++++++++++++++++++++++++---
drivers/infiniband/hw/mlx4/srq.c | 8 ++++
drivers/net/bonding/bond_main.c | 28 +++++--------
include/linux/mlx4/device.h | 2 +
include/net/bonding.h | 2 +-
8 files changed, 210 insertions(+), 25 deletions(-)
next reply other threads:[~2015-02-08 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 9:49 Or Gerlitz [this message]
2015-02-08 9:49 ` [PATCH V1 net-next 1/3] net/bonding: Fix potential bad memory access during bonding events Or Gerlitz
2015-02-08 9:49 ` [PATCH V1 net-next 2/3] IB/mlx4: Always use the correct port for mirrored multicast attachments Or Gerlitz
2015-02-08 9:49 ` [PATCH V1 net-next 3/3] IB/mlx4: Reset flow support for IB kernel ULPs Or Gerlitz
2015-02-09 22:04 ` [PATCH V1 net-next 0/3] bonding and mlx4 fixes for the HA/LAG support and mlx4 reset flow David Miller
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=1423388974-9635-1-git-send-email-ogerlitz@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roland@kernel.org \
--cc=talal@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).