Re: [PATCH] bridge: mdb: avoid uninitialized variable warning

From: Arnd Bergmann Date: Wed, 10 Feb 2016 16:09:02 +0100 > A recent change to the mdb code confused the compiler to the point > where it did not realize that the port-group returned from > br_mdb_add_group() is always valid when the function returns a nonzero > return value, so

Re: [PATCH] bridge: mdb: avoid uninitialized variable warning

From: Arnd Bergmann Date: Wed, 10 Feb 2016 16:09:02 +0100 > A recent change to the mdb code confused the compiler to the point > where it did not realize that the port-group returned from > br_mdb_add_group() is always valid when the function returns a nonzero > return value, so we get a

[PATCH] bridge: mdb: avoid uninitialized variable warning

A recent change to the mdb code confused the compiler to the point where it did not realize that the port-group returned from br_mdb_add_group() is always valid when the function returns a nonzero return value, so we get a spurious warning: net/bridge/br_mdb.c: In function 'br_mdb_add':

[PATCH] bridge: mdb: avoid uninitialized variable warning

A recent change to the mdb code confused the compiler to the point where it did not realize that the port-group returned from br_mdb_add_group() is always valid when the function returns a nonzero return value, so we get a spurious warning: net/bridge/br_mdb.c: In function 'br_mdb_add':