boards/feather-nrf52840*: rename to adafruit-feather-nrf52840-*#21349
boards/feather-nrf52840*: rename to adafruit-feather-nrf52840-*#21349crasbe merged 2 commits intoRIOT-OS:masterfrom
Conversation
857b8d2 to
ae71300
Compare
|
The Also the Edit: I found those with |
|
Thanks for double-checking, should be fixed now. |
|
You could use the opportunity to adapt the headers according to #21335, but that's no must. Personally I think the warning introduced in #21242 should've been red because now you don't really notice it, but that's too late now I guess 😅 I'm not sure if it would be better to name the fixup PRs something like Otherwise everything looks good to me, I can physically test it when I'm home with the nRF52840DK pretending to be a Feather. |
f398aa8 to
69fbe83
Compare
I'd rather not, to be honest, to keep the changes small for this commit. Still waiting for @KSKNico to provide the next subtree PR :)
It's never too late: #21352
I've now squashed them together anyways. |
|
This is the cause of the build failure. Apparently with |
|
100 ways to break your builds :P |
|
Updated to 120 bytes and confirmed to still work with |
90e49d3 to
efef39f
Compare
|
...and was so free to squash already |
|
I'm still not super happy that everything is one commit, but I don't think it's necessary to split it up again. |
efef39f to
49abc17
Compare
49abc17 to
e92ac97
Compare
|
Thanks for your review! |
Contribution description
While we are in spring cleaning mood, and with #21242 in, let's make use of the board alias feature to start renaming boards in a backward-compatible way according to RDM0003.
Testing procedure
CI should automatically start using the new board names for all tests except
tests/build_system/board_aliaswhich automatically tests the new board aliases. You can test the working aliases locally by using the oldBOARDnamesfeather-nrf52840andfeather-nrf52840-sense.