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.

Sign up for GitHub

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

Jump to bottom

Fix mk0_avr_extra PIN_COMPATIBLE lint warning #19640

Merged
merged 1 commit into from
Jan 20, 2023
Merged

Fix mk0_avr_extra PIN_COMPATIBLE lint warning #19640

merged 1 commit into from
Jan 20, 2023

Conversation

zvecr
Copy link
Member

@zvecr zvecr commented Jan 19, 2023 •
edited
Loading

Description

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@zvecr zvecr requested a review from a team January 19, 2023 21:54
@zvecr zvecr added the bug label Jan 19, 2023
@zvecr zvecr merged commit cc9a3a8 into develop Jan 20, 2023
@zvecr zvecr deleted the zvecr-patch-2 branch January 20, 2023 02:02
omikronik pushed a commit to omikronik/qmk_firmware that referenced this pull request Jan 22, 2023
@zvecr @omikronik
Fix mk0_avr_extra PIN_COMPATIBLE lint warning (qmk#19640)
fa8af4f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fauxpark fauxpark fauxpark approved these changes

Assignees
No one assigned
Labels
bug keyboard
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@zvecr @fauxpark