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

[Keyboard] Use DIRECT_PINS instead of empty MATRIX_ROW_PINS: sixshooter #8130

Merged
merged 2 commits into from
Feb 11, 2020

Conversation

elfmimi
Copy link
Contributor

@elfmimi elfmimi commented Feb 9, 2020

Description

In the config.h of sixshooter, it has been defined as following.
#define MATRIX_ROWS 1
#define MATRIX_ROW_PINS { }
This is a potential bug because by definition row_pins will get assigned undefined value.

In this case use of DIRECT_PINS is appropriate.

Similar to #8115, I need this consistency for my next PR.

Types of Changes

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

Checklist

  • My code follows the code style of this project.
  • 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).

Copy link
Member

@zvecr zvecr left a comment

Choose a reason for hiding this comment

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

@zvecr zvecr added the keyboard label Feb 10, 2020
@elfmimi
Copy link
Contributor Author

elfmimi commented Feb 10, 2020

I don’t think that’s necessary when there is only a single row.
Should I really change?

@zvecr
Copy link
Member

zvecr commented Feb 10, 2020

when there is only a single row

The single row way was a hangover from before DIRECT_PINS existed.
Given the physical layout is 2x3, it would be my preference. It makes stuff like a future via config more logical.

@elfmimi
Copy link
Contributor Author

elfmimi commented Feb 10, 2020

I got what you mean.

Copy link
Member

@zvecr zvecr left a comment

Choose a reason for hiding this comment

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

Perfect, thanks for that

@drashna drashna merged commit 4b7d46c into qmk:master Feb 11, 2020
HokieGeek pushed a commit to HokieGeek/qmk_firmware that referenced this pull request Feb 21, 2020
…er (qmk#8130)

* [Keyboard] Use DIRECT_PINS instead of empty MATRIX_ROW_PINS: sixshooter

* [Keyboard] Reform the matrix into 2x3: sixshooter
c0psrul3 pushed a commit to c0psrul3/qmk_firmware that referenced this pull request Mar 23, 2020
…er (qmk#8130)

* [Keyboard] Use DIRECT_PINS instead of empty MATRIX_ROW_PINS: sixshooter

* [Keyboard] Reform the matrix into 2x3: sixshooter
kylekuj pushed a commit to kylekuj/qmk_firmware that referenced this pull request Apr 21, 2020
…er (qmk#8130)

* [Keyboard] Use DIRECT_PINS instead of empty MATRIX_ROW_PINS: sixshooter

* [Keyboard] Reform the matrix into 2x3: sixshooter
jakeisnt pushed a commit to jakeisnt/qmk_firmware that referenced this pull request Aug 20, 2020
…er (qmk#8130)

* [Keyboard] Use DIRECT_PINS instead of empty MATRIX_ROW_PINS: sixshooter

* [Keyboard] Reform the matrix into 2x3: sixshooter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants