| Age | Commit message (Collapse) | Author |
|---|
|
* Remove rgblight_list defines with no usage
* Remove rgblight_setrgb_*[_at] defines
* Remove rgblight_sethsv_* defines
* Remove rgblight_sethsv_noeeprom_* defines
* Delete rgblight_list.h and remove all references
|
|
* `KC_SLCK` -> `KC_SCRL`
* `KC_NLCK` -> `KC_NUM`
|
|
|
|
* Add ARRAY_SIZE and CEILING utility macros
* Apply a coccinelle patch to use ARRAY_SIZE
* fix up some straggling items
* Fix 'make test:secure'
* Enhance ARRAY_SIZE macro to reject acting on pointers
The previous definition would not produce a diagnostic for
```
int *p;
size_t num_elem = ARRAY_SIZE(p)
```
but the new one will.
* explicitly get definition of ARRAY_SIZE
* Convert to ARRAY_SIZE when const is involved
The following spatch finds additional instances where the array is
const and the division is by the size of the type, not the size of
the first element:
```
@ rule5a using "empty.iso" @
type T;
const T[] E;
@@
- (sizeof(E)/sizeof(T))
+ ARRAY_SIZE(E)
@ rule6a using "empty.iso" @
type T;
const T[] E;
@@
- sizeof(E)/sizeof(T)
+ ARRAY_SIZE(E)
```
* New instances of ARRAY_SIZE added since initial spatch run
* Use `ARRAY_SIZE` in docs (found by grep)
* Manually use ARRAY_SIZE
hs_set is expected to be the same size as uint16_t, though it's made
of two 8-bit integers
* Just like char, sizeof(uint8_t) is guaranteed to be 1
This is at least true on any plausible system where qmk is actually used.
Per my understanding it's universally true, assuming that uint8_t exists:
https://stackoverflow.com/questions/48655310/can-i-assume-that-sizeofuint8-t-1
* Run qmk-format on core C files touched in this branch
Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
|
|
|
|
`QMK_KEYS_PER_SCAN` (#15292)
|
|
* Updated RGB Matrix suspend define part 3
* Revert "Update config.h for kbdfans/kbd67/mkiirgb/v3 (#13978)"
This reverts commit 80015f7fb023f27ad5307815fd5433694a3bcb4a.
* Add additional boards/keymaps
|
|
Co-authored-by: Drashna Jaelre <drashna@live.com>
|
|
* VIA Support: LFKPad
* Condense two mostly redundant rules.mk files
* Set BOOTMAGIC_ENABLE to lite as advised by VIA tutorial
|
|
|
|
|
|
* Remove/migrate action_get_macro()s from default keymaps
* Leave these breaks alone
|
|
* Cleanup Default Keymaps to conform to QMK Firmware standards
* Minor fixes
* Revert some changes
|
|
|
|
* Make layer_info weak so it works with QMK Configurator
* Fix lfk87 compile issue
* Add fixes for lfkpad
|
|
|
|
* LFKPad: matrix refactor
* LFKPad: keymap refactor (QMK_KEYBOARD_H; matrix update)
* LFKPad: Configurator support
* LFKPad: added community layout numpad_6x4 to rules.mk
* LFKPad: Update rgb_sequence to match new matrix
* LFKPad: delete deprecated makefile include block from rules.mk
|
|
* change diverge 3 KC_KEYMAP to LAYOUT
* Change KEYMAP to LAYOUT for handwired arrow pad
* change M10A to LAYOUT for m10-a
* Change KC_KEYMAP to LAYOUT_kc and KEYMAP to LAYOUT for mf68
* change KC_KEYMAP to LAYOUT for nano
* Refactor to LAYOUT
* refactor to LAYOUT-ansi and LAYOUT_iso for s65
* LAYOUT conversions for lfkkeyboards
* missed a few renames
* mini1800 for lfkeyobards support of LAYOUT
|
|
* Update smk65 fn layer, add iso
* Added Fn layer to ISO keymap
* Fix error when backlight is disabled but lighting isn't
* Remove broke mini1800 iso map
* Add keymaps
* Add LFKPad
* Add split delete to lfk78
* Typo
* Custom keymap
|
