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

fix(driver): Fix broken compilation for MAX7318 driver #1921

Merged
merged 2 commits into from
Sep 28, 2023

Conversation

zhiayang
Copy link
Contributor

@zhiayang zhiayang commented Sep 3, 2023

The driver got neglected and didn't compile. Now it does (:

Tested to work on real hardware.

EDIT: what's the best way to make a CI test for this so that it keeps being compiled?

@zhiayang zhiayang requested a review from a team as a code owner September 3, 2023 20:06
@caksoylar caksoylar added the bug Something isn't working label Sep 25, 2023
@petejohanson
Copy link
Contributor

EDIT: what's the best way to make a CI test for this so that it keeps being compiled?

We would need a board or shield in-tree that has the driver enabled, and add that to the core-coverage.yml file, which drives our regression suite during CI for PRs.

Copy link
Contributor

@petejohanson petejohanson left a comment

Choose a reason for hiding this comment

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

Thanks!

@petejohanson petejohanson merged commit 9b3d2cb into zmkfirmware:main Sep 28, 2023
19 checks passed
@zhiayang zhiayang deleted the max7318-fix branch September 28, 2023 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants