[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190206190814.GC1442@otheros>
Date: Wed, 6 Feb 2019 20:08:14 +0100
From: Linus Lüssing <linus.luessing@...3.blue>
To: The list for a Better Approach To Mobile Ad-hoc
Networking <b.a.t.m.a.n@...ts.open-mesh.org>
Cc: netdev@...r.kernel.org, Jiri Pirko <jiri@...lanox.com>
Subject: Re: [B.A.T.M.A.N.] [RFC v4 00/19] batman-adv: netlink restructuring,
part 2
On Wed, Feb 06, 2019 at 07:20:25PM +0100, Sven Eckelmann wrote:
> On Tuesday, 5 February 2019 20.24.10 CET Linus Lüssing wrote:
> [...]
> > Another thought, if all this is too vague for now...
>
> Yes, it is to vague for the integration in netlink :D
>
> > what about
> > ommiting the BATADV_ATTR_MULTICAST_(MODE)_ENABLED for now and use
> > a reverse logic instead? Like
> > BATADV_ATTR_MULTICAST_FORCEFLOOD_ENABLED, defaulting to false.
>
> Would be fine for me. But it is rather odd to map this to the batctl
> multicast_mode. But the name is explaining quite well what it does
> and you can later rewrite the batctl part.
Ok, will rewrite the batctl part later then. And probably keep "batctl
mm" as a (hidden?) option for compatibility reasons?
Regards, Linus
Powered by blists - more mailing lists