Skip to content

SocketCAN: Enable error frames #384

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

Merged

Conversation

christiansandberg
Copy link
Collaborator

Fixes #375.

@codecov
Copy link

codecov bot commented Aug 6, 2018

Codecov Report

Merging #384 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #384      +/-   ##
===========================================
+ Coverage     59.3%   59.31%   +<.01%     
===========================================
  Files           55       55              
  Lines         4241     4242       +1     
===========================================
+ Hits          2515     2516       +1     
  Misses        1726     1726

@felixdivo felixdivo added the bug label Aug 6, 2018
@felixdivo
Copy link
Collaborator

Should this option be exposed to the user?

@christiansandberg
Copy link
Collaborator Author

Most other interfaces do not have an option for that either, so the application should always be able to handle error frames anyway.

@christiansandberg christiansandberg merged commit 2920ff5 into hardbyte:develop Aug 6, 2018
@christiansandberg christiansandberg deleted the socketcan-error-frames branch August 6, 2018 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants