Downgraded one log level from warn! to trace! ...#230
Merged
thejpster merged 1 commit intoMar 2, 2026
Merged
Conversation
…te returned from CMD0 initialization
Merged
via the queue into
rust-embedded-community:develop
with commit Mar 2, 2026
c3950a0
7 checks passed
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
2 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.
... when other-than expected byte returned from CMD0 initialization.
I am but one user of this crate, however using my particular SD Card + reader, the current logging scheme results in a flurry of yellow "warning"-level log messages 100% of the time during project initialization for what is, as best as I can tell, a completely expected scenario.
Given that this initialization occurs in a finite retry loop which return an
Erronce the retries are exceeded, might it make sense to downgrade the log level of this particular message?