docs: Add pointers to final Kconfig/devicetree files #2796
Merged
Conversation
This file contains 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
Nick-Munnich
approved these changes
Jan 25, 2025
caksoylar
commented
Jan 25, 2025
caksoylar
force-pushed
the
docs/diagnose-steps
branch
2 times, most recently
from
42ec9e8 to
0912710
Compare
caksoylar
force-pushed
the
docs/diagnose-steps
branch
from
0912710 to
ad6fa61
Compare
jpinsent
pushed a commit
to jpinsent/zmk
that referenced
this pull request
Jan 28, 2025
docs: Add diagnosis pointers for Kconfig/devicetree outputs docs: Add tip boxes for diagnosing config/devicetree changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a section on diagnosing (unexpected) build results via looking at final Kconfig/devicetree files that are displayed during the build. Also add pointers to this section in Configuration overview where these two types of files are talked about.