Mem barrier #148
Merged
Mem barrier #148
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
lipengfei28
requested review from
xiaoxiang781216 and
GUIDINGLI
as code owners
lipengfei28
force-pushed
the
mem_barrier
branch
5 times, most recently
from
c67be20 to
8647529
Compare
|
@lipengfei28 please fix ci error. |
Signed-off-by: lipengfei28 <[email protected]>
Signed-off-by: lipengfei28 <[email protected]>
Signed-off-by: lipengfei28 <[email protected]>
Signed-off-by: lipengfei28 <[email protected]>
Signed-off-by: lipengfei28 <[email protected]>
Signed-off-by: lipengfei28 <[email protected]>
Signed-off-by: lipengfei28 <[email protected]>
Signed-off-by: lipengfei28 <[email protected]>
lipengfei28
force-pushed
the
mem_barrier
branch
from
8647529 to
b80f2cb
Compare
xiaoxiang781216
approved these changes
Jan 15, 2025
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.
use UP_xx as memory barrier standard api
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.