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
cleanup(driver/ppm_fillers.c): create consistencies (u16 to uint16_t) #1437
cleanup(driver/ppm_fillers.c): create consistencies (u16 to uint16_t) #1437
Conversation
Please double check driver/API_VERSION file. See versioning. /hold |
Thank you for this! After merging this #1435 we have a conflict with master so you need to rebase :/ |
@ecbadeaux also need a rebase here, ty! |
Signed-off-by: Everett Badeaux <everettc1810@gmail.com>
@incertum Should be good now please approve! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: f84814f8441fe2a0f70cf180485bacefa8d93be3
|
/milestone next-driver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ecbadeaux, FedeDP, incertum The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |
What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area driver-kmod
Does this PR require a change in the driver versions?
No.
What this PR does / why we need it:
Make driver code more consistent. (u16 -> uint16_t)
Which issue(s) this PR fixes:
part of #902
(partial fix other issues still remain in 902)
Special notes for your reviewer:
Going to be gradually creating integer consistency across the codebase. Best to keep the reviews small.
Tagging @dwindsor for visibility.
Does this PR introduce a user-facing change?: