-
Notifications
You must be signed in to change notification settings - Fork 217
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
Fix #392, Make OS_STREAM_STATE available with APIs #393
Fix #392, Make OS_STREAM_STATE available with APIs #393
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.
Recommend rebase when the API scrub pull request gets merged, and then add doxygen comments to document the states/typedef per the API scrub implemented pattern.
Confused, is there a separate ticket/pull request for an API scrub? If so, have a ticket #? |
It's in the current integration candidate #375, was the fix to #364... pull request was #371. I think just pending @astrogeco merge of #375. |
@CDKnightNASA recommend a rebase now that #375 is merged, and just add comments that follow the current pattern. Or I can add them if you want. |
9849a4a
to
f0fae6a
Compare
rebased, commented, and squashed |
f0fae6a
to
1cca69f
Compare
CCB 2020-04-01 - APPROVED |
@CDKnightNASA - why close? They close when the update gets to master... |
Whoops, I mean when the pull request gets to the IC branch |
Closing the pull request, not the issue. Will create a new pull request that incorporates the 3 related tickets, plus going to wait for #405 |
Ohhhh, perfect! My mistake. When I first clicked I thought it was the issue. |
…it's needed by OS_SelectSingle()
Describe the contribution
moves OS_STREAM_STATE defines to os/inc/osapi-os-core.h as they're needed by OS_SelectSingle()
Testing performed
Can build unit tests (being developed) for OS_SelectSingle()
Note that this is a prerequisite for #377 and is related to #391 all three should be pulled at the same time, or #392, #391 then #377
Contributor Info - All information REQUIRED for consideration of pull request
[email protected]