[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121204085320.3e08986a@nehalam.linuxnetplumber.net>
Date: Tue, 4 Dec 2012 08:53:20 -0800
From: Stephen Hemminger <shemminger@...tta.com>
To: Cong Wang <amwang@...hat.com>
Cc: netdev@...r.kernel.org, bridge@...ts.linux-foundation.org,
Herbert Xu <herbert@...dor.hengli.com.au>,
"David S. Miller" <davem@...emloft.net>,
Thomas Graf <tgraf@...g.ch>,
Jesper Dangaard Brouer <brouer@...hat.com>
Subject: Re: [PATCH net-next v2] bridge: export multicast database via
netlink
On Mon, 3 Dec 2012 21:03:43 +0800
Cong Wang <amwang@...hat.com> wrote:
> V2: drop patch 1/2, export ifindex directly
> Redesign netlink attributes
> Improve netlink seq check
> Handle IPv6 addr as well
>
> TODO: remove debugging printk's
>
> This patch exports bridge multicast database via netlink
> message type RTM_GETMDB. Similar to fdb, but currently bridge-specific.
> We may need to support modify multicast database too (RTM_{ADD,DEL}MDB).
>
> Cc: Herbert Xu <herbert@...dor.apana.org.au>
> Cc: Stephen Hemminger <shemminger@...tta.com>
> Cc: "David S. Miller" <davem@...emloft.net>
> Cc: Thomas Graf <tgraf@...g.ch>
> Cc: Jesper Dangaard Brouer <brouer@...hat.com>
> Signed-off-by: Cong Wang <amwang@...hat.com>
>
Minor nit reported by checkpatch was the messages should be using the api
which provides the most info in the log to identify.
WARNING: Prefer netdev_info(netdev, ... then dev_info(dev, ... then pr_info(... to printk(KERN_INFO ...
#190: FILE: net/bridge/br_mdb.c:28:
+ printk(KERN_INFO "no router on bridge\n")
There is a set of macro's already for use in bridging code:
br_info(br, "no router on bridge\n");
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists