-
Notifications
You must be signed in to change notification settings - Fork 349
schedule: fix address space mismatches #7286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
+8
−7
Conversation
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
Collaborator
Author
|
SOFCI TEST |
dbaluta
approved these changes
Mar 16, 2023
marcinszkudlinski
requested changes
Mar 16, 2023
Contributor
marcinszkudlinski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good change to Zephyr kernel types no need however to play with cached/uncached aliases. Wasn't __sparse_cache macros dedicated to avoid warnings?
lyakh
requested changes
Mar 16, 2023
Collaborator
275d695 to
ff8e074
Compare
Fix below sparse warnings: zephyr_dp_schedule.c:134:20: warning: incorrect type in argument 1 (different address spaces) zephyr_dp_schedule.c:348:36: warning: incorrect type in assignment (different address spaces) introduced by 3ee1d78 Signed-off-by: Chao Song <chao.song@linux.intel.com>
kv2019i
approved these changes
Mar 17, 2023
marcinszkudlinski
approved these changes
Mar 17, 2023
lyakh
approved these changes
Mar 17, 2023
lgirdwood
approved these changes
Mar 17, 2023
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.
Fix below sparse warnings:
zephyr_dp_schedule.c:134:20: warning: incorrect type in argument 1 (different address spaces)
zephyr_dp_schedule.c:348:36: warning: incorrect type in assignment (different address spaces)
introduced by 3ee1d78