common: skip warning: 'No bad blocks found' #6127
Open
+50
−11
Conversation
This file contains 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
Skip warning: "Cannot find any matching device, no bad blocks found" when pmem2_badblock_next() is used internally. Signed-off-by: Tomasz Gromadzki <[email protected]>
grom72
added
Priority: 1 urgent
DAOS
grom72
force-pushed
the
6126-no-warning-on-pool-open
branch
3 times, most recently
from
013fe94
to
10254e1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Skip warning: "Cannot find any matching device, no bad blocks found" when pmem2_badblock_next() is used internally.
Fixes: #6126
This change is