Re: [PATCH net-next v2 3/3] net: bridge: export supported boolopts

2018-11-24 Thread Andrew Lunn
On Sat, Nov 24, 2018 at 04:34:22AM +0200, Nikolay Aleksandrov wrote: > Now that we have at least one bool option, we can export all of the > supported bool options via optmask when dumping them. > > v2: new patch > > Signed-off-by: Nikolay Aleksandrov Reviewed-by: Andrew Lunn Andrew

Re: [PATCH net-next v2 3/3] net: bridge: export supported boolopts

2018-11-24 Thread nikolay
On 24 November 2018 18:16:47 EET, Andrew Lunn wrote: >On Sat, Nov 24, 2018 at 04:34:22AM +0200, Nikolay Aleksandrov wrote: >> Now that we have at least one bool option, we can export all of the >> supported bool options via optmask when dumping them. >> >Hi Nik > >That answers my question then...

Re: [PATCH net-next v2 3/3] net: bridge: export supported boolopts

2018-11-24 Thread Andrew Lunn
On Sat, Nov 24, 2018 at 04:34:22AM +0200, Nikolay Aleksandrov wrote: > Now that we have at least one bool option, we can export all of the > supported bool options via optmask when dumping them. > Hi Nik That answers my question then... I'm assuming this means there is no easy way to generate a

[PATCH net-next v2 3/3] net: bridge: export supported boolopts

2018-11-23 Thread Nikolay Aleksandrov
Now that we have at least one bool option, we can export all of the supported bool options via optmask when dumping them. v2: new patch Signed-off-by: Nikolay Aleksandrov --- net/bridge/br.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/bridge/br.c b/net/bridge/br.c in