From: Stephen Hemminger <stephen@networkplumber.org>
To: Scott Feldman <sfeldma@gmail.com>
Cc: "Roopa Prabhu" <roopa@cumulusnetworks.com>,
"Jiří Pírko" <jiri@resnulli.us>,
"Jamal Hadi Salim" <jhs@mojatatu.com>,
"Benjamin LaHaise" <bcrl@kvack.org>,
"Thomas Graf" <tgraf@suug.ch>,
"john fastabend" <john.fastabend@gmail.com>,
"John Linville" <linville@tuxdriver.com>,
"vyasevic@redhat.com" <vyasevic@redhat.com>,
Netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"shm@cumulusnetworks.com" <shm@cumulusnetworks.com>,
"Andy Gospodarek" <gospo@cumulusnetworks.com>
Subject: Re: [PATCH v3 iproute2] bridge link: add option 'self'
Date: Wed, 24 Dec 2014 12:30:25 -0800 [thread overview]
Message-ID: <20141224123025.2af99b41@urahara> (raw)
In-Reply-To: <CAE4R7bCDTmR_zaVredZNzviaXc1YzXtSAK3dYj+BekiW9OKSpQ@mail.gmail.com>
On Sat, 6 Dec 2014 09:12:51 -0800
Scott Feldman <sfeldma@gmail.com> wrote:
> Signed-of-by: Scott Feldman <sfeldma@gmail.com>
>
> On Sat, Dec 6, 2014 at 12:21 AM, <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.
> >
> > v1 -> v2
> > - fix a few bugs. Initialize flags to zero: this was required to
> > keep the current behaviour unchanged.
> >
> > v2 -> v3
> > - fix comment
> >
> > Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Applied to post 3.18 current tree.
next prev parent reply other threads:[~2014-12-24 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 8:21 [PATCH v3 iproute2] bridge link: add option 'self' roopa
2014-12-06 17:12 ` Scott Feldman
2014-12-24 20:30 ` Stephen Hemminger [this message]
2014-12-08 11:06 ` Jiri Pirko
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=20141224123025.2af99b41@urahara \
--to=stephen@networkplumber.org \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--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=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).