-
Notifications
You must be signed in to change notification settings - Fork 3k
Initialize the interface at the construction #8975
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
nsapi_error_t result = interface.initialize(&NanostackRfPhy::get_default_instance()); | ||
if (result != 0) { | ||
tr_error("LoWPANND initialize failed: %d", error); | ||
return NULL; |
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.
Missing singleton_unlock
here.
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.
Sinleton_unlock's has been added
that it's done only once.
78b94f9
to
f7de4a4
Compare
need more work |
Don't need more work, can be proceed |
@KariHaapalehto Will start once all RC3 PRs are in. Out of curiosity, what changed in the past five days that indicated that this no longer needed more work? |
@kjbracey-arm It sounds like this is ready for a re-review. |
I was testing this locally with mbed-os-mesh-minimal and just before I left for extended weekend I notice, that change didn't compile with mesh_6lowpan.json-config. So I did changed status to "need work". |
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
and make sure that it's done only once.
Description
Interface is initialized at construction.
This will make it possible to read mac-address before mesh.connect()
Tested locally that correction is working with mbed-os-example-mesh-minimal and K66F
Pull request type