From: Sathya Perla <sathya.perla@avagotech.com>
To: netdev@vger.kernel.org
Subject: [PATCH net-next v2 02/10] be2net: avoid configuring VEPA mode on BE3
Date: Mon, 28 Dec 2015 01:49:16 -0500 [thread overview]
Message-ID: <1451285364-9074-3-git-send-email-sathya.perla@avagotech.com> (raw)
In-Reply-To: <1451285364-9074-1-git-send-email-sathya.perla@avagotech.com>
From: Suresh Reddy <suresh.reddy@avagotech.com>
BE3 chip doesn't support VEPA mode.
Signed-off-by: Suresh Reddy <suresh.reddy@avagotech.com>
Signed-off-by: Sathya Perla <sathya.perla@avagotech.com>
---
drivers/net/ethernet/emulex/benet/be_main.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/ethernet/emulex/benet/be_main.c b/drivers/net/ethernet/emulex/benet/be_main.c
index 34e324f..2f76cbe 100644
--- a/drivers/net/ethernet/emulex/benet/be_main.c
+++ b/drivers/net/ethernet/emulex/benet/be_main.c
@@ -5108,6 +5108,9 @@ static int be_ndo_bridge_setlink(struct net_device *dev, struct nlmsghdr *nlh,
return -EINVAL;
mode = nla_get_u16(attr);
+ if (BE3_chip(adapter) && mode == BRIDGE_MODE_VEPA)
+ return -EOPNOTSUPP;
+
if (mode != BRIDGE_MODE_VEPA && mode != BRIDGE_MODE_VEB)
return -EINVAL;
--
2.4.1
next prev parent reply other threads:[~2015-12-28 6:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 6:49 [PATCH net-next v2 00/10] be2net: patch set Sathya Perla
2015-12-28 6:49 ` [PATCH net-next v2 01/10] be2net: fix VF link state transition from disabled to auto Sathya Perla
2015-12-28 6:49 ` Sathya Perla [this message]
2015-12-28 6:49 ` [PATCH net-next v2 03/10] be2net: cleanup FW flash image related macro defines Sathya Perla
2015-12-28 6:49 ` [PATCH net-next v2 04/10] be2net: move FW flash cmd code to be_cmds.c Sathya Perla
2015-12-28 6:49 ` [PATCH net-next v2 05/10] be2net: log digital signature errors while flashing FW image Sathya Perla
2015-12-28 8:23 ` kbuild test robot
2015-12-28 6:49 ` [PATCH net-next v2 06/10] be2net: remove a line of code that has no effect Sathya Perla
2015-12-28 6:49 ` [PATCH net-next v2 07/10] be2net: remove unused error variables Sathya Perla
2015-12-28 6:49 ` [PATCH net-next v2 08/10] be2net: fix port-res desc query of GET_PROFILE_CONFIG FW cmd Sathya Perla
2015-12-28 6:49 ` [PATCH net-next v2 09/10] be2net: support ethtool get-dump option Sathya Perla
2015-12-28 6:49 ` [PATCH net-next v2 10/10] be2net: bump up the driver version to 11.0.0.0 Sathya Perla
2015-12-29 20:50 ` [PATCH net-next v2 00/10] be2net: patch set David Miller
2015-12-30 6:27 ` Sathya Perla
2015-12-30 17:44 ` 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=1451285364-9074-3-git-send-email-sathya.perla@avagotech.com \
--to=sathya.perla@avagotech.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).