-
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
Kconfig: Expose gnrc/netif configurations #13065
Kconfig: Expose gnrc/netif configurations #13065
Conversation
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.
It looks good. examples/gnrc_networking
builds as usual and configurations can be changed via Kconfig.
Just one comment: you skipped two occurrences of GNRC_NETIF_IPV6_ADDRS_NUMOF
:
tests/gnrc_sock_dns/Makefile:34
examples/gnrc_minimal/Makefile:27
a007a0c
to
b966ec2
Compare
@leandrolanzieri thanks for the review. I addressed your comments. |
The message for b966ec2 seems to be too long 😕 |
4debfca
to
cce97a0
Compare
cce97a0
to
0e951fa
Compare
0e951fa
to
fb71ccc
Compare
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.
I did a few greps and all macros appear to be changed now (with the correct prefix). ACK!
Contribution description
This PR moves the configuration macros of
gnrc_netif
found here to theCONFIG_
namespace, and exposes them to Kconfig.As agreed offline with @leandrolanzieri I did not include the default thread priority parameter because this should be defined by the platform, if not changed manually. We might need a better solution to this in future.
Furthermore, I did not include
GNRC_NETIF_NUMOF
because this won't be static anymore in the future.Testing procedure
examples/gnrc_networking
should still work as usual.make menuconfig
in the test application.Issues/PRs references
Part of #12888