From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: netdev@vger.kernel.org, matanb@mellanox.com, amirv@mellanox.com,
talal@mellanox.com, roland@kernel.org, yishaih@mellanox.com
Subject: Re: [PATCH V1 net-next 0/9] mlx4: Fix and enhance the device reset flow
Date: Sun, 25 Jan 2015 14:46:29 -0800 (PST) [thread overview]
Message-ID: <20150125.144629.226865788722084962.davem@davemloft.net> (raw)
In-Reply-To: <1422197983-16048-1-git-send-email-ogerlitz@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Sun, 25 Jan 2015 16:59:34 +0200
> This series from Yishai Hadas fixes the device reset flow and adds SRIOV support.
Series applied, thanks.
prev parent reply other threads:[~2015-01-25 22:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 14:59 [PATCH V1 net-next 0/9] mlx4: Fix and enhance the device reset flow Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 1/9] net/mlx4_core: Maintain a persistent memory for mlx4 device Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 2/9] net/mlx4_core: Set device configuration data to be persistent across reset Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 3/9] net/mlx4_core: Refactor the catas flow to work per device Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 4/9] net/mlx4_core: Enhance the catas flow to support device reset Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 5/9] net/mlx4_core: Activate reset flow upon fatal command cases Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 6/9] net/mlx4_core: Manage interface state for Reset flow cases Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 7/9] net/mlx4_core: Handle AER flow properly Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 8/9] net/mlx4_core: Enable device recovery flow with SRIOV Or Gerlitz
2015-01-25 14:59 ` [PATCH V1 net-next 9/9] net/mlx4_core: Reset flow activation upon SRIOV fatal command cases Or Gerlitz
2015-01-25 22:46 ` David Miller [this message]
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=20150125.144629.226865788722084962.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roland@kernel.org \
--cc=talal@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).