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

sixaxis updates #2

Merged
merged 2 commits into from Feb 23, 2019
Merged

sixaxis updates #2

merged 2 commits into from Feb 23, 2019

Conversation

psyke83
Copy link
Member

@psyke83 psyke83 commented Feb 21, 2019

This was causing conflicts with potential EXIT_FAILURE return states
(e.g. if the open or read functions failed).

This was causing conflicts with potential EXIT_FAILURE return states
(e.g. if the open or read functions failed).
@psyke83 psyke83 changed the title sixaxis-timeout: send correct exit code on success sixaxis updates Feb 22, 2019
Certain applications grab exclusive control of the input event node;
check for this case and ensure that the timeout is not a false-
positive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant