tlsr82: disable CONFIG_RW_SPINLOCK#14308
Closed
W-M-R wants to merge 1 commit into
Closed
Conversation
tlsr82 does not support atomic include/nuttx/spinlock.h:45:25: fatal error: stdatomic.h: No such file or directory Signed-off-by: chao an <anchao@xiaomi.com>
github-actions
Bot
added
Board: arm
Size: XS
GUIDINGLI
reviewed
Oct 15, 2024
| # CONFIG_NSH_DISABLE_SEMICOLON is not set | ||
| # CONFIG_NSH_DISABLE_UNAME is not set | ||
| # CONFIG_NSH_DISABLE_XD is not set | ||
| # CONFIG_RW_SPINLOCK is not set |
Contributor
There was a problem hiding this comment.
The message should be "enable" ?
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
3 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.
Summary
tlsr82 does not support atomic
include/nuttx/spinlock.h:45:25: fatal error: stdatomic.h: No such file or directory
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.