Skip to content
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

Correct return code mismatches in CFE #1705

Closed
jphickey opened this issue Jul 23, 2021 · 0 comments · Fixed by #1706 or #1701
Closed

Correct return code mismatches in CFE #1705

jphickey opened this issue Jul 23, 2021 · 0 comments · Fixed by #1706 or #1701
Assignees
Milestone

Comments

@jphickey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
In several places across CFE, a function is documented as returning a CFE status (e.g. CFE_SUCCESS) but checked against either OS_SUCCESS or CFE_PSP_SUCCESS, or vice versa.

Describe the solution you'd like
Functions documented as returning CFE status should check for CFE_SUCCESS, where functions documented as returning an OSAL status should check for OS_SUCCESS, and functions returning a PSP status should check for CFE_PSP_SUCCESS.

Additional context
Similar to #1698, but found in more places. Since the definition of all these symbols is 0, this is no change in practice, but should be fixed for correctness sake.

Requester Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this Jul 23, 2021
jphickey added a commit to jphickey/cFE that referenced this issue Jul 23, 2021
Make sure functions documented as CFE status check for CFE_SUCCESS,
and functions documented as OSAL status check for OS_SUCCESS.
astrogeco added a commit that referenced this issue Jul 29, 2021
paulober pushed a commit to paulober/cFE that referenced this issue Aug 1, 2021
Make sure functions documented as CFE status check for CFE_SUCCESS,
and functions documented as OSAL status check for OS_SUCCESS.
@skliper skliper added this to the 7.0.0 milestone Sep 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants