From: David Ahern <dsahern@gmail.com>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, ivecera@redhat.com,
nikolay@cumulusnetworks.com, stephen@networkplumber.org
Subject: Re: [PATCH iproute2 net-next v3 0/2] support for bridge fdb and neigh get
Date: Tue, 1 Oct 2019 09:30:40 -0600 [thread overview]
Message-ID: <02c6ab60-fbf6-49d7-7e6f-f50b8b7d86d8@gmail.com> (raw)
In-Reply-To: <1569905543-33478-1-git-send-email-roopa@cumulusnetworks.com>
On 9/30/19 10:52 PM, Roopa Prabhu wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This series adds iproute2 support to lookup a bridge fdb and
> neigh entry.
> example:
> $bridge fdb get 02:02:00:00:00:03 dev test-dummy0 vlan 1002
> 02:02:00:00:00:03 dev test-dummy0 vlan 1002 master bridge
>
> $ip neigh get 10.0.2.4 dev test-dummy0
> 10.0.2.4 dev test-dummy0 lladdr de:ad:be:ef:13:37 PERMANENT
>
>
> v2 - remove cast around stdout in print_fdb as pointed out by stephen
>
> v3 - add Tested by Ivan. and address feedback from david ahern
>
>
> Roopa Prabhu (2):
> bridge: fdb get support
> ipneigh: neigh get support
>
> bridge/fdb.c | 113 +++++++++++++++++++++++++++++++++++++++++++++++-
> ip/ipneigh.c | 72 ++++++++++++++++++++++++++++--
> man/man8/bridge.8 | 35 +++++++++++++++
> man/man8/ip-neighbour.8 | 25 +++++++++++
> 4 files changed, 240 insertions(+), 5 deletions(-)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2019-10-01 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 4:52 [PATCH iproute2 net-next v3 0/2] support for bridge fdb and neigh get Roopa Prabhu
2019-10-01 4:52 ` [PATCH iproute2 net-next v3 1/2] bridge: fdb get support Roopa Prabhu
2019-10-01 14:59 ` Stephen Hemminger
2019-10-02 16:07 ` Roopa Prabhu
2019-10-01 4:52 ` [PATCH iproute2 net-next v3 2/2] ipneigh: neigh " Roopa Prabhu
2019-10-01 15:30 ` David Ahern [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=02c6ab60-fbf6-49d7-7e6f-f50b8b7d86d8@gmail.com \
--to=dsahern@gmail.com \
--cc=ivecera@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.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).