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 - the remainder of unreachable code warnings, and random small fixes #905

Merged
merged 34 commits into from
Nov 28, 2020

Conversation

jimklimov
Copy link
Member

Follows up from #823 / #844 efforts to remove several classes of warnings from being seen in NUT build reports.

@jimklimov jimklimov force-pushed the fightwarn-unreachable-code branch from 58522aa to debb1a2 Compare November 26, 2020 09:51
…piler warnings with "ifndef HAVE___ATTRIBUTE__NORETURN" to avoid opposite warnings now
…iler warnings with "ifndef HAVE___ATTRIBUTE__NORETURN" to avoid opposite warnings now
…iler warnings with "ifndef HAVE___ATTRIBUTE__NORETURN" to avoid opposite warnings now
@jimklimov jimklimov force-pushed the fightwarn-unreachable-code branch from debb1a2 to 9140376 Compare November 26, 2020 14:44
@jimklimov
Copy link
Member Author

At least partially tested for nut-scanner fixes (in the overall fightwarn effort branch applied) for discovery of nutclient, SNMP and NetXML devices - these worked. An USB driver for two ports was occupied and two port-busy reports appeared. (With offending drivers stopped, a re-run of nut-scanner discovered these devices).

@jimklimov jimklimov merged commit d87c2fd into networkupstools:master Nov 28, 2020
@jimklimov jimklimov deleted the fightwarn-unreachable-code branch November 28, 2020 13:03
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.

1 participant