zephyr: fix build warning in CI tests#21
Open
pillo79 wants to merge 1 commit into
Open
Conversation
|
|
Checking a constant non-zero value at runtime will always generate a "warning: the address of xxx will never be null" from the compiler. Instead, ensure the device is present using DT_NODE_HAS_STATUS_OKAY at compile time and provide a nicer feedback to the user.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checking a constant non-zero value at runtime will always generate a
warning: the address of xxx will never be nullfrom the compiler. Instead, ensure the device is present usingDT_NODE_HAS_STATUS_OKAYat compile time and provide a nicer feedback to the user.