nvme-print-stdout: Add hexadecimal value 0x prefix #2238
Merged
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
ikegami-t
force-pushed
the
prefix-0x
branch
3 times, most recently
from
c2f7784 to
26073f8
Compare
|
I'm a bit worried about the changing the format from |
This resolves checkpatch line length exceeding warning. Signed-off-by: Tokunori Ikegami <[email protected]>
The output printed with the 0x prefix but as not hexadecimal. Signed-off-by: Tokunori Ikegami <[email protected]>
Also channge 64bit value to use %#"PRIx64" instead of 0x%"PRIx64". Signed-off-by: Tokunori Ikegami <[email protected]>
|
Just reverted to |
|
Thanks! |
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.
Also unify to use %#x or %#"PRIx64" instead of 0x%x and 0x%"PRIx64".