From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/3] be2net: patch set
Date: Fri, 1 Aug 2014 17:47:29 +0530 [thread overview]
Message-ID: <1406895452-29514-1-git-send-email-sathya.perla@emulex.com> (raw)
Patch 1 fixes a regression caused by a previous commit on net-next.
Old versions of BE3 FW may not support cmds to re-provision (and hence
optimize) resources/queues in SR-IOV config. Do not treat this FW cmd
failure as fatal and fail the function initialization. Instead, just
enable SR-IOV with the resources provided by the FW.
Patch 2 ignores a VF mac address setting if the new mac is already active
on the VF.
Patch 3 adds support to delete a FW-dump via ethtool on Lancer adapters.
Please consider applying this patch-set to the net-next tree. Thanks!
Kalesh AP (1):
be2net: support deleting FW dump via ethtool (only for Lancer)
Sathya Perla (1):
be2net: ignore get/set profile FW cmd failures
Vasundhara Volam (1):
be2net: ignore VF mac address setting for the same mac
drivers/net/ethernet/emulex/benet/be.h | 2 +
drivers/net/ethernet/emulex/benet/be_cmds.c | 48 ++++++++++++++-
drivers/net/ethernet/emulex/benet/be_cmds.h | 10 +++
drivers/net/ethernet/emulex/benet/be_ethtool.c | 17 +++---
drivers/net/ethernet/emulex/benet/be_main.c | 75 ++++++++++++++----------
5 files changed, 109 insertions(+), 43 deletions(-)
next reply other threads:[~2014-08-01 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 12:17 Sathya Perla [this message]
2014-08-01 12:17 ` [PATCH net-next 1/3] be2net: ignore get/set profile FW cmd failures Sathya Perla
2014-08-01 12:17 ` [PATCH net-next 2/3] be2net: ignore VF mac address setting for the same mac Sathya Perla
2014-08-01 12:17 ` [PATCH net-next 3/3] be2net: support deleting FW dump via ethtool (only for Lancer) Sathya Perla
2014-08-02 22:59 ` [PATCH net-next 0/3] be2net: patch set David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-03-04 5:44 Sathya Perla
2015-03-04 20:59 ` David Miller
2015-03-26 7:05 Sathya Perla
2015-03-29 19:34 ` 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=1406895452-29514-1-git-send-email-sathya.perla@emulex.com \
--to=sathya.perla@emulex.com \
--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;
as well as URLs for NNTP newsgroup(s).