Re: trunk shouldnt care if it's stacked

2019-01-10 Thread Martin Pieuchot
On 09/01/19(Wed) 19:12, Theo de Raadt wrote: > Philip Guenther wrote: > > > On Wed, Jan 9, 2019 at 1:11 AM Klemens Nanni wrote: > > > > > On Wed, Jan 09, 2019 at 01:12:31PM +1000, David Gwynne wrote: > > > > -#define TRUNK_MAX_STACKING 4 /* maximum number of stacked > > > trunks */ > >

Re: trunk shouldnt care if it's stacked

2019-01-09 Thread Theo de Raadt
Philip Guenther wrote: > On Wed, Jan 9, 2019 at 1:11 AM Klemens Nanni wrote: > > > On Wed, Jan 09, 2019 at 01:12:31PM +1000, David Gwynne wrote: > > > -#define TRUNK_MAX_STACKING 4 /* maximum number of stacked > > trunks */ > > Is this an arbitrary limit or does it conceal other limitia

Re: trunk shouldnt care if it's stacked

2019-01-09 Thread Philip Guenther
On Wed, Jan 9, 2019 at 1:11 AM Klemens Nanni wrote: > On Wed, Jan 09, 2019 at 01:12:31PM +1000, David Gwynne wrote: > > -#define TRUNK_MAX_STACKING 4 /* maximum number of stacked > trunks */ > Is this an arbitrary limit or does it conceal other limitiations? > If stacking is handled via

Re: trunk shouldnt care if it's stacked

2019-01-09 Thread Klemens Nanni
On Wed, Jan 09, 2019 at 01:12:31PM +1000, David Gwynne wrote: > -#define TRUNK_MAX_STACKING 4 /* maximum number of stacked trunks */ Is this an arbitrary limit or does it conceal other limitiations? The commit that added it lacks this information: revision 1.2 date: 2005/0

trunk shouldnt care if it's stacked

2019-01-08 Thread David Gwynne
nothing else does, and i want to clean up the code. ok? Index: if_trunk.c === RCS file: /cvs/src/sys/net/if_trunk.c,v retrieving revision 1.137 diff -u -p -r1.137 if_trunk.c --- if_trunk.c 12 Aug 2018 23:50:31 - 1.137 +++ i