From: Jiri Pirko <jiri@resnulli.us>
To: roopa@cumulusnetworks.com
Cc: sfeldma@gmail.com, jhs@mojatatu.com, bcrl@kvack.org,
tgraf@suug.ch, john.fastabend@gmail.com,
stephen@networkplumber.org, linville@tuxdriver.com,
vyasevic@redhat.com, netdev@vger.kernel.org, davem@davemloft.net,
shm@cumulusnetworks.com, gospo@cumulusnetworks.com
Subject: Re: [PATCH net-next v5 3/3] bridge: remove mode BRIDGE_MODE_SWDEV
Date: Tue, 9 Dec 2014 08:56:29 +0100 [thread overview]
Message-ID: <20141209075629.GD1974@nanopsycho.orion> (raw)
In-Reply-To: <1418076261-24593-4-git-send-email-roopa@cumulusnetworks.com>
Mon, Dec 08, 2014 at 11:04:21PM CET, roopa@cumulusnetworks.com wrote:
>From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
>This patch removes bridge mode swdev.
>Users can use BRIDGE_FLAGS_SELF to indicate swdev offload
>if needed.
>
>Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Thanks Roopa for taking care of this!
>---
> include/uapi/linux/if_bridge.h | 1 -
> 1 file changed, 1 deletion(-)
>
>diff --git a/include/uapi/linux/if_bridge.h b/include/uapi/linux/if_bridge.h
>index 05f0869..b03ee8f 100644
>--- a/include/uapi/linux/if_bridge.h
>+++ b/include/uapi/linux/if_bridge.h
>@@ -105,7 +105,6 @@ struct __fdb_entry {
>
> #define BRIDGE_MODE_VEB 0 /* Default loopback mode */
> #define BRIDGE_MODE_VEPA 1 /* 802.1Qbg defined VEPA mode */
>-#define BRIDGE_MODE_SWDEV 2 /* Full switch device offload */
> #define BRIDGE_MODE_UNDEF 0xFFFF /* mode undefined */
>
> /* Bridge management nested attributes
>--
>1.7.10.4
>
prev parent reply other threads:[~2014-12-09 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 22:04 [PATCH net-next v5 3/3] bridge: remove mode BRIDGE_MODE_SWDEV roopa
2014-12-08 22:44 ` Scott Feldman
2014-12-09 7:56 ` Jiri Pirko [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=20141209075629.GD1974@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=jhs@mojatatu.com \
--cc=john.fastabend@gmail.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=shm@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
--cc=vyasevic@redhat.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