lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 12 Jan 2015 16:47:39 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	roopa@...ulusnetworks.com
Cc:	netdev@...r.kernel.org, shemminger@...tta.com, vyasevic@...hat.com,
	wkok@...ulusnetworks.com, sfeldma@...il.com
Subject: Re: [PATCH net-next v3 0/4] bridge: support for vlan range in
 setlink/dellink

From: roopa@...ulusnetworks.com
Date: Sat, 10 Jan 2015 07:31:11 -0800

> From: Roopa Prabhu <roopa@...ulusnetworks.com>
> 
> This series adds new flags in IFLA_BRIDGE_VLAN_INFO to indicate
> vlan range.
> 
> Will post corresponding iproute2 patches if these get accepted.
> 
> v1-> v2
>     - changed patches to use a nested list attribute
>     IFLA_BRIDGE_VLAN_INFO_LIST as suggested by scott feldman
>     - dropped notification changes from the series. Will post them
>     separately after this range message is accepted.
> 
> v2 -> v3
>     - incorporated some review feedback
>     - include patches to fill vlan ranges during getlink
>     - Dropped IFLA_BRIDGE_VLAN_INFO_LIST. I think it may get
>     confusing to userspace if we introduce yet another way to
>     send lists. With getlink already sending nested
>     IFLA_BRIDGE_VLAN_INFO in IFLA_AF_SPEC, It seems better to
>     use the existing format for lists and just use the flags from v2
>     to mark vlan ranges
> 
> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
> Signed-off-by: Wilson Kok <wkok@...ulusnetworks.com>

This looks fine to me, series applied, thanks.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ