From: David Miller <davem@davemloft.net>
To: razor@blackwall.org
Cc: shm@cumulusnetworks.com, nikolay@cumulusnetworks.com,
netdev@vger.kernel.org, roopa@cumulusnetworks.com,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next 00/20] bridge: complete netlink support
Date: Sun, 04 Oct 2015 16:47:08 -0700 (PDT) [thread overview]
Message-ID: <20151004.164708.1245786027485004311.davem@davemloft.net> (raw)
In-Reply-To: <1443961427-15085-1-git-send-email-razor@blackwall.org>
From: Nikolay Aleksandrov <razor@blackwall.org>
Date: Sun, 4 Oct 2015 14:23:27 +0200
> This set completes the bridge device's netlink support and makes it
> possible to view and configure everything that can be configured via
> sysfs. I have tested all of these (setting and getting). There're a few
> longer line warnings about the br_get_size() ifla comments but I think we
> should have them to know what has been accounted for. I have used the sysfs
> interface as a guide of what and how to set. As usual I'll send the
> corresponding iproute2 patches later.
> The bridge port's netlink interface will be completed after this set gets
> applied in some form.
>
> This patch-set is on top of my last vlan cleanups set:
> http://www.spinics.net/lists/netdev/msg346005.html
Series applied, thanks.
prev parent reply other threads:[~2015-10-04 23:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 12:23 [PATCH net-next 00/20] bridge: complete netlink support Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 01/20] bridge: netlink: add group_fwd_mask support Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 02/20] bridge: netlink: export root id Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 03/20] bridge: netlink: export bridge id Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 04/20] bridge: netlink: export root port Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 05/20] bridge: netlink: export root path cost Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 06/20] bridge: netlink: export topology_change and topology_change_detected Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 07/20] bridge: netlink: export all timers Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 08/20] bridge: netlink: add group_addr support Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 09/20] bridge: netlink: add fdb flush Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 10/20] bridge: netlink: add support for multicast_router Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 11/20] bridge: netlink: add support for multicast_snooping Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 12/20] bridge: netlink: add support for multicast_query_use_ifaddr Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 13/20] bridge: netlink: add support for multicast_querier Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 14/20] bridge: netlink: add support for igmp's hash_elasticity Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 15/20] bridge: netlink: add support for igmp's hash_max Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 16/20] bridge: netlink: add support for multicast_last_member_count Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 17/20] bridge: netlink: add support for multicast_startup_query_count Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 18/20] bridge: netlink: add support for igmp's intervals Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 19/20] bridge: netlink: add support for netfilter tables config Nikolay Aleksandrov
2015-10-04 12:23 ` [PATCH net-next 20/20] bridge: netlink: add support for default_pvid Nikolay Aleksandrov
2015-10-04 23:47 ` David Miller [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=20151004.164708.1245786027485004311.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=razor@blackwall.org \
--cc=roopa@cumulusnetworks.com \
--cc=shm@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;
as well as URLs for NNTP newsgroup(s).