[lwip-devel] [bug #19347] netif_add & tcpip_init problem

[Jonathan Larmour]

Follow-up Comment #11, bug #19347 (project lwip):

Ok, that's all fair enough, and I'll say that I only had 4 hours sleep last
night, and that's my excuse ;-).

Nevertheless, I think it's ok to just insist that netif_add should only be
done _after_ tcpip_init_done (from the callback directly or by some other
means). By just making that a fact of policy, we can get rid of these
checks.

I think you using messages for this so the tcpip thread does it, but
controlled by a configuration option, is an excellent idea. That completely
resolves my concern - adding more code to support behaviour that most people
don't need. Thanks for working on it.

And I wasn't trying to suggest that you didn't have a real job :-). From your
comment, I realise it may have read that way. What I really meant was a job
where one can't justify playing around with lwIP all day during work hours.
But anyway, we're furiously agreeing now.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?19347>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/