Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

types: Fix EOM header optional data present fields definition #802

Merged
merged 2 commits into from
Mar 26, 2024

Conversation

ikegami-t
Copy link
Contributor

Defined eye data present as bit 0 and printable eye present as bit 1. Fixed eye data present to bit 1 and printable eye present to bit 0. Add the optional data present reserved filed definition and macros to get.

@ikegami-t
Copy link
Contributor Author

Note: The existing NVME_EOM_EYE_DATA_PRESENT and NVME_EOM_PRINTABLE_EYE_PRESENT macros have been changed.

Copy link
Contributor

@bpaupore-wdc bpaupore-wdc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change seem mostly good to me, though wouldn't removing the original enums cause backwards-compatibility issues?

I'm not sure if this feature is new enough to just do it anyways, or if renaming the macros and fixing but keeping the original definitions would be best.

@igaw
Copy link
Collaborator

igaw commented Mar 25, 2024

I agree, better leave the old enums around and avoid breakage. Just add a 'deprecated' comment to them.

Defined eye data present as bit 0 and printable eye present as bit 1.
Fixed eye data present to bit 1 and printable eye present to bit 0.

Signed-off-by: Tokunori Ikegami <ikegami.t@gmail.com>
Also add reserved filed definition and macros to get.

Signed-off-by: Tokunori Ikegami <ikegami.t@gmail.com>
@ikegami-t
Copy link
Contributor Author

Thanks for your review comments. Just fixed the patch as mentioned.

@igaw igaw merged commit 691f809 into linux-nvme:master Mar 26, 2024
14 checks passed
@igaw
Copy link
Collaborator

igaw commented Mar 26, 2024

Thanks!

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.

3 participants