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

Use string literals for SERIAL_NUMBER #13403

Merged
merged 2 commits into from Jul 16, 2021

Conversation

fauxpark
Copy link
Member

@fauxpark fauxpark commented Jul 1, 2021

Description

This is safe to do as literally 0 boards currently in the repo make use of SERIAL_NUMBER. This makes a good demo for doing the same to MANUFACTURER and PRODUCT so that things like:
https://github.com/qmk/qmk_firmware/blob/master/keyboards/exclusive/e6v2/le/config.h#L28
evaluate correctly (or rather, aren't evaluated at all).

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).

@fauxpark fauxpark requested a review from a team July 1, 2021 11:23
@drashna drashna requested a review from a team July 1, 2021 17:00
@fauxpark fauxpark merged commit 7ed5ac4 into qmk:develop Jul 16, 2021
@fauxpark fauxpark deleted the string-literal-serial-number branch July 16, 2021 09:43
nhongooi pushed a commit to nhongooi/qmk_firmware that referenced this pull request Dec 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants