-
Notifications
You must be signed in to change notification settings - Fork 3k
Correct LWIP_DEBUG definition #4997
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
Conversation
Commit f602c93 incorrectly started defining LWIP_DEBUG as either 0 or 1. lwipopts.h locally was changed to use #if, but all existing users continued to use #ifdef. Therefore defining it to 0 was accidentally enabling it for quite a few users. This would have pulled in some unwanted lwIP code, and affected some drivers, eg k64f_emac.c allocating an extra 2K of stack. Correct lwipopts.h to either define it as 1 or leave it undefined, and change the #if tests back to #ifdef, so all are consistent.
cc @hasnainvirk |
cc @yogpan01 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
/morph test-nightly |
1 similar comment
/morph test-nightly |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
Commit f602c93 incorrectly started defining
LWIP_DEBUG
as either0
or1
.lwipopts.h locally was changed to use
#if
, but all existing users continued to use#ifdef
. Therefore defining it to0
was accidentally enabling it for quite a few users.This would have pulled in some unwanted lwIP code, and affected some drivers, eg k64f_emac.c allocating an extra 2K of stack.
Correct lwipopts.h to either define it as
1
or leave it undefined, and change the#if
tests back to#ifdef
, so all are consistent.