Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Kernel.h doxygen update #8435
referenced this pull request
Oct 17, 2018
I'm unsure what the current "state-of-the-art" of "interrupt safety" documentation is. Is there a current equivalent of this page? https://docs.mbed.com/docs/mbed-os-handbook/en/5.2/concepts/thread_safety/ ? I see some files still use those terms.
So I'm not even sure if we should be tinkering with this wording (which a lot of files use) or using something totally different.
If we are tinkering this this wording, "may" seems more formally correct to me than "can", so I'm not particularly keen on the change. Obviously you /can/ - no-one can stop you - but are you permitted to?
I think this is one for @AnotherButler, really, but...
And yes, no idea why anyone would want to call those from ISR - I expect the docs are the result of someone inspecting what looked like it would work and annotating.
The equivalent of that page is https://os.mbed.com/docs/latest/porting/thread-safety-and-porting.html
Nov 6, 2018
Note: This PR is now a part of a rollup PR (#8663).
No further work is needed here, as once that PR is merged, this PR will also be closed and marked as merged.
If any more commits are made in this PR, this PR will remain open and have to go through CI on its own.