hcnmgr: Fix hexdump format. #72
Closed
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
When the file contains multiple consecutive bytes of the same value hexdump squeezes them replacing all but first with * Use the -v argument to avoid this problem. Also put the hexdump invocation into a function. Signed-off-by: Michal Suchanek <msuchanek@suse.de>
|
Tested-by: Mingming Cao mmc@linux.vnet.ibm.com |
|
Fixed in commit a8420c2 |
|
Corrected commit id on next branch 4d56ac2 |
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.
When the file contrains multiple consecutive same bytes the /1 format
shows them abbreviated with *. To avoid this problem use 4/1 format.
Also put the hexdump invocation into a function.
Signed-off-by: Michal Suchanek msuchanek@suse.de