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,
nhorman@tuxdriver.com, nicolas.dichtel@6wind.com,
vyasevic@redhat.com, f.fainelli@gmail.com,
buytenh@wantstofly.org, aviadr@mellanox.com,
netdev@vger.kernel.org, davem@davemloft.net,
shm@cumulusnetworks.com, gospo@cumulusnetworks.com
Subject: Re: [PATCH iproute2] bridge link: add option 'self'
Date: Fri, 5 Dec 2014 08:55:59 +0100 [thread overview]
Message-ID: <20141205075559.GC1866@nanopsycho.orion> (raw)
In-Reply-To: <1417746436-41023-1-git-send-email-roopa@cumulusnetworks.com>
Fri, Dec 05, 2014 at 03:27:16AM CET, roopa@cumulusnetworks.com wrote:
>From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
>Currently self is set internally only if hwmode is set.
>This makes it necessary for the hw to have a mode.
>There is no hwmode really required to go to hardware. So, introduce
>self for anybody who wants to target hardware.
Signed-off line is missing.
Other than that, the patch looks fine.
Reviewed-by: Jiri Pirko <jiri@resnulli.us>
Feel free to add my review line to the repost.
>---
> bridge/link.c | 3 +++
> 1 file changed, 3 insertions(+)
>
>diff --git a/bridge/link.c b/bridge/link.c
>index 90d9e7f..2b86141 100644
>--- a/bridge/link.c
>+++ b/bridge/link.c
>@@ -321,6 +321,9 @@ static int brlink_modify(int argc, char **argv)
> "\"veb\".\n");
> exit(-1);
> }
>+ } else if (strcmp(*argv, "self") == 0) {
>+ NEXT_ARG();
>+ flags = BRIDGE_FLAGS_SELF;
> } else {
> usage();
> }
>--
>1.7.10.4
>
next prev parent reply other threads:[~2014-12-05 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 2:27 [PATCH iproute2] bridge link: add option 'self' roopa
2014-12-05 6:52 ` Scott Feldman
2014-12-05 7:04 ` Roopa Prabhu
2014-12-05 7:55 ` Jiri Pirko [this message]
2014-12-05 13:46 ` Roopa Prabhu
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=20141205075559.GC1866@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=aviadr@mellanox.com \
--cc=bcrl@kvack.org \
--cc=buytenh@wantstofly.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=jhs@mojatatu.com \
--cc=john.fastabend@gmail.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nicolas.dichtel@6wind.com \
--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;
as well as URLs for NNTP newsgroup(s).