boards/nucleo: fix Cortex-M4F family in doc page#21561
Merged
crasbe merged 2 commits intoRIOT-OS:masterfrom Jun 24, 2025
Merged
boards/nucleo: fix Cortex-M4F family in doc page#21561crasbe merged 2 commits intoRIOT-OS:masterfrom
crasbe merged 2 commits intoRIOT-OS:masterfrom
Conversation
github-actions
bot
added
Area: doc
crasbe
added
Type: enhancement
crasbe
approved these changes
Jun 23, 2025
Contributor
|
I think you could squash the three nucleo commits to something like |
krzysztof-cabaj
force-pushed
the
nucleo-fix-M4F-family
branch
from
d4579c5 to
01ce1e8
Compare
Contributor
Author
|
Done. |
Contributor
Author
|
@crasbe Thanks for support! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution description
This PR fix family for Nucleo boards with Cortex-M4 with FPU, family changed to Cortex-M4F.
The issue was spotted in PR #21554 (comment) .
Testing procedure
Generate doc and check if everything looks good, for example:
Issues/PRs references
#21554 (comment)