From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: --to=stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 v2] bridge fdb: add 'use' option to set NTF_USE flag in fdb add requests
Date: Fri, 31 Jul 2015 18:11:59 -0700 [thread overview]
Message-ID: <20150731181159.2ffc00e4@urahara> (raw)
In-Reply-To: <1438292222-45993-1-git-send-email-roopa@cumulusnetworks.com>
On Thu, 30 Jul 2015 14:37:02 -0700
Roopa Prabhu <roopa@cumulusnetworks.com> wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This is similar to command options corresponding to other NTF_* flags
> already exposed to the user space (examples self/master).
>
> Also updates bridge man page (The man page patch also includes
> a fix to the 'self' entry and documents 'master' for fdb entries)
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Applied thanks.
prev parent reply other threads:[~2015-08-01 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 21:37 [PATCH iproute2 v2] bridge fdb: add 'use' option to set NTF_USE flag in fdb add requests Roopa Prabhu
2015-07-31 8:05 ` Nikolay Aleksandrov
2015-08-01 1:11 ` Stephen Hemminger [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=20150731181159.2ffc00e4@urahara \
--to=stephen@networkplumber.org \
--cc=--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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