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

Fightwarn fallthrough questionable - upscode2 #846

Conversation

jimklimov
Copy link
Member

@jimklimov jimklimov commented Nov 8, 2020

  • drivers/upscode2.c: comment the fallthrough in upsc_simple() switch, so far consider it explicitly desired as it was before

Discovered thanks to CI improvements from #844

…so far consider it explicitly desired as it was before
@jimklimov jimklimov changed the title drivers/upscode2.c: comment the fallthrough in upsc_simple() switch, … Fightwarn fallthrough questionable - upscode2 Nov 8, 2020
@lgtm-com
Copy link

lgtm-com bot commented Nov 8, 2020

This pull request introduces 2 alerts when merging 43f8fb6 into 8c1ad08 - view on LGTM.com

new alerts:

  • 2 for FIXME comment

Copy link
Member

@clepple clepple left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No idea, but this driver has been around for a while, so I suspect someone would have noticed if the behavior was not correct.

@jimklimov
Copy link
Member Author

New code wording does same logic as the old code did, but without warnings. If this did not explode in the years before so someone would complain, probably the logic is right indeed.

@jimklimov jimklimov merged commit a2cd5a1 into networkupstools:master Nov 11, 2020
@jimklimov jimklimov deleted the fightwarn-fallthrough-questionable-upscode2 branch November 15, 2020 10:41
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.

2 participants