-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkg/lwip: fix adaption to API change of netdev_new_api #21091
pkg/lwip: fix adaption to API change of netdev_new_api #21091
Conversation
0fb00bd
to
04589cd
Compare
I tested again after the last force push, still works as before. I originally assumed that this was just not adapted to the new API; it was, but just a few lines where it should have come. |
Since RIOT-OS#21012 a netdev in the new API can return > 0 directly in netdev_driver_t::send() to indicate the driver is naturally synchronous and has already completed the transmission. The adaption of lwIP to that API change contained a bug: It handled the case after the thread is already blocked waiting for the signal that is never going to arrive. This is now fixed.
04589cd
to
424eae0
Compare
And another force-push: Rewording the commit title. (No retesting required, as no code changed.) |
You can also drop the |
It could be set to an error other than RIOT/pkg/lwip/contrib/netdev/lwip_netdev.c Line 312 in 424eae0
|
Thx 🎉 |
Contribution description
Since #21012 a netdev in the new API can return > 0 directly in netdev_driver_t::send() to indicate the driver is naturally synchronous and has already completed the transmission.
The adaption of lwIP to that API change contained a bug: It handled the case after the thread is already blocked waiting for the signal that is never going to arrive. This is now fixed.
Testing procedure
In
master
This PR
Issues/PRs references
#21012