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

Move OS_FS_ERR_* defines to common os error definitions #262

Closed
skliper opened this issue Sep 30, 2019 · 3 comments · Fixed by #423 or #440
Closed

Move OS_FS_ERR_* defines to common os error definitions #262

skliper opened this issue Sep 30, 2019 · 3 comments · Fixed by #423 or #440
Assignees
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Sep 30, 2019

OS_DirectoryOpen returns OS_INVALID_POINTER if dir_id or path pointers are NULL.

OS_DirectoryRead returns OS_FS_ERR_INVALID_POINTER if dirent pointer is NULL.

Likely other cases of mixed use. Suggest deprecation of the OS_FS_ERR_* defines and switch to common definitions.

@skliper skliper added this to the osal-5.0.1 milestone Sep 30, 2019
@skliper skliper self-assigned this Sep 30, 2019
@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Imported from trac issue 239. Created by jhageman on 2019-08-23T14:59:31, last modified: 2019-08-23T14:59:31

@skliper skliper added the bug label Sep 30, 2019
@skliper skliper modified the milestones: osal-5.0.1, osal-5.1.0 Sep 30, 2019
@skliper skliper removed their assignment Sep 30, 2019
@skliper skliper added enhancement and removed bug labels Oct 16, 2019
@skliper
Copy link
Contributor Author

skliper commented Oct 22, 2019

Related to #118. Really should deprecate the OS_FS_* defines that aren't unique to FS.

@ejtimmon
Copy link

A handful of apps use OS_FS_SUCCESS and/or OS_FS_ERROR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment