On Sun, Jul 01, 2012 at 02:05:14PM +0200, Sven Eckelmann wrote:
The structure batadv_priv grows everytime a new feature is introduced. It gets hard to find the parts of the struct that belongs to a specific feature. This becomes even harder by the fact that not every feature uses a prefix in the member name.
The variables for bridge loop avoidence, gateway handling, translation table and visualization server are moved into separate structs that are included in the bat_priv main struct.
Signed-off-by: Sven Eckelmann sven@narfation.org
Any other ideas for substructs?
Hello Sven,
first of all thank you for taking care of this.
For what concerns the TT substructure it is fine with me, I had some doubt about the ranaming of certain fields (ttvn -> tt.vn, and tt_crc -> tt.crc), but I think they are ok.
Cheers,