[RFC PATCH 0/5] Add AF_BRIDGE support to link cache

[roopa at cumulusnetworks.com]

From: roopa <roopa at cumulusnetworks.com>

This patch series lists three approaches to adding AF_BRIDGE support
to libnl. All have been tested to work. Sending this as RFC to solicit
feedback.

Each of the patchsets for the three series have been generated separately
on tip-of-tree. Combined them all into one series just to have them in
one common place.

First approach:
  [PATCH 1/5] Add support for AF_BRIDGE family in link cache
	This patch adds support for AF_BRIDGE family in link cache
	and adds link family attribute to link object oo_id_attrs.
	With this the key for link object lookups will be ifindex and family.
	This allows for base rtnl link objects to co-exist with the AF_BRIDGE
	link objects in the same cache

Second approach:
  [PATCH 2/5] Add support for updating objects in the cache
  [PATCH 3/5] Add AF_BRIDGE object update support to link cache
	Since AF_BRIDGE link object attributes can be merged with the AF_UNSPEC
	link objects attributes, this patch updates existing link cache objects
	with AF_BRIDGE attributes

Third approach:
  [PATCH 4/5] Add support for a new bridge link cache route/bridge_link
  [PATCH 5/5] Make cache manager event handling continue looking if a cache returned NL_SKIP
	This series adds a separate bridge link cache 'route/bridge_link'
	for bridge port link management

Signed-off-by: Roopa Prabhu <roopa at cumulusnetworks.com>
Reviewed-by: Nolan Leake <nolan at cumulusnetworks.com>
Reviewed-by: Shrijeet Mukherjee <shm at cumulusnetworks.com>
Reviewed-by: Wilson Kok <wkok at cumulusnetworks.com>
	
roopa (5):
  1/5 Add support for AF_BRIDGE family in link cache
  2/5 Add support for updating objects in the cache
  3/5 Add AF_BRIDGE object update support to link cache
  4/5 Add support for a new bridge link cache route/bridge_link
  5/5 Make cache manager event handling continue looking if a cache returned NL_SKIP

-- 
1.7.2.5