From: roopa <roopa@cumulusnetworks•com>
To: Thomas Graf <tgraf@suug•ch>
Cc: netdev@vger•kernel.org, shemminger@vyatta•com,
vyasevic@redhat•com, wkok@cumulusnetworks•com, sfeldma@gmail•com
Subject: Re: [PATCH net-next v3 3/3] bridge: new function to pack vlans into ranges during gets
Date: Mon, 12 Jan 2015 15:52:30 -0800 [thread overview]
Message-ID: <54B45E3E.4030508@cumulusnetworks.com> (raw)
In-Reply-To: <20150112234751.GA16617@casper.infradead.org>
On 1/12/15, 3:47 PM, Thomas Graf wrote:
> On 01/10/15 at 07:31am, roopa@cumulusnetworks•com wrote:
>> From: Roopa Prabhu <roopa@cumulusnetworks•com>
>>
>> This patch adds new function to pack vlans into ranges
>> whereever applicable using the flags BRIDGE_VLAN_INFO_RANGE_BEGIN
>> and BRIDGE VLAN_INFO_RANGE_END
>>
>> Old vlan packing code is moved to a new function and continues to be
>> called when filter_mask is RTEXT_FILTER_BRVLAN.
>>
>> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks•com>
> Roopa,
>
> Just came across these new warnings:
>
> net/bridge/br_netlink.c: In function ‘br_fill_ifinfo’:
> net/bridge/br_netlink.c:146:32: warning: ‘vid_range_flags’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> err = br_fill_ifvlaninfo_range(skb, vid_range_start,
> ^
> net/bridge/br_netlink.c:108:6: note: ‘vid_range_flags’ was declared here
> u16 vid_range_flags;
sorry abt that, patch coming...in a few mins. compiling...
Don't remember seeing it during my compilation...
Thanks!
prev parent reply other threads:[~2015-01-12 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 15:31 [PATCH net-next v3 3/3] bridge: new function to pack vlans into ranges during gets roopa
2015-01-12 23:47 ` Thomas Graf
2015-01-12 23:52 ` roopa [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=54B45E3E.4030508@cumulusnetworks.com \
--to=roopa@cumulusnetworks$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfeldma@gmail$(echo .)com \
--cc=shemminger@vyatta$(echo .)com \
--cc=tgraf@suug$(echo .)ch \
--cc=vyasevic@redhat$(echo .)com \
--cc=wkok@cumulusnetworks$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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