Skip to content

Conversation

sc108-lee
Copy link

Some control files use nvme-cli version 2.6.4,
where the csts value is output as "csts : 1" even though it represents a hexadecimal value (%x format). Later versions and the latest release output the value with a "0x" prefix (e.g., "csts : 0x1").

Update the parser to correctly interpret the csts value as hexadecimal regardless of the format.

Some control files use nvme-cli version 2.6.4,
where the csts value is output as "csts : 1" even though it represents a hexadecimal value (%x format).
Later versions and the latest release output the value with a "0x" prefix (e.g., "csts : 0x1").

Update the parser to correctly interpret the csts value as hexadecimal regardless of the format.

Signed-off-by: Steven Seungcheol Lee <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant