-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[onewire] adjust loglevel #7935
Conversation
Signed-off-by: Jan N. Klug <[email protected]>
I'm kinda on the fence about this. On the one hand, bindings shouldn't be logging errors in general, but on the other hand an error might be appropriate here since it means something has gone wrong with how the core is bootstrapping the binding. |
Travis tests were successfulHey @J-N-K, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpmeister It does not matter too much as both logging levels will be visible to the user.
And as the message says that it "might" not work, a warning seems to be the better choice indeed.
Signed-off-by: Jan N. Klug <[email protected]> Signed-off-by: CSchlipp <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]> Signed-off-by: MPH80 <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]> Signed-off-by: Daan Meijer <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]>
Adjust log level to coding guidelines
Signed-off-by: Jan N. Klug [email protected]