Re: second wave of netlink extended ACK reporting

2017-04-16 Thread David Ahern
On 4/16/17 8:40 AM, Jamal Hadi Salim wrote: > > Johannes or anybody else working on it? > i.e one which sends the extack to the bowels of callees > so we can return meaningful messages > example: rtnetlink::doit() or equivalent seems to be a candidate for > taking it as a param > For things that c

Re: second wave of netlink extended ACK reporting

2017-04-16 Thread David Ahern
On 4/16/17 8:48 AM, Jamal Hadi Salim wrote: > Excellent. His patches seem to be in. Seems > commit ce07183282975026716107d36fd3f5f93de76668 > is a good point? yes. will send later today.

Re: second wave of netlink extended ACK reporting

2017-04-16 Thread Jamal Hadi Salim
On 17-04-16 10:45 AM, David Ahern wrote: On 4/16/17 8:40 AM, Jamal Hadi Salim wrote: Johannes or anybody else working on it? i.e one which sends the extack to the bowels of callees so we can return meaningful messages example: rtnetlink::doit() or equivalent seems to be a candidate for taking i

Re: second wave of netlink extended ACK reporting

2017-04-16 Thread David Ahern
On 4/16/17 8:40 AM, Jamal Hadi Salim wrote: > > Johannes or anybody else working on it? > i.e one which sends the extack to the bowels of callees > so we can return meaningful messages > example: rtnetlink::doit() or equivalent seems to be a candidate for > taking it as a param I have a patch for

second wave of netlink extended ACK reporting

2017-04-16 Thread Jamal Hadi Salim
Johannes or anybody else working on it? i.e one which sends the extack to the bowels of callees so we can return meaningful messages example: rtnetlink::doit() or equivalent seems to be a candidate for taking it as a param For things that call netlink_ack it may be easier if they create the extac