Skip to content

Conversation

@aiChaoSONG
Copy link
Collaborator

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

@aiChaoSONG aiChaoSONG changed the title [skip ci][DNM]schedule: fix address space mismatches schedule: fix address space mismatches Mar 16, 2023
@aiChaoSONG
Copy link
Collaborator Author

SOFCI TEST

@aiChaoSONG aiChaoSONG requested review from kv2019i and lyakh March 16, 2023 04:11
@aiChaoSONG aiChaoSONG marked this pull request as ready for review March 16, 2023 08:20
Copy link
Contributor

@marcinszkudlinski marcinszkudlinski left a 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?

@marc-hb
Copy link
Collaborator

marc-hb commented Mar 16, 2023

@aiChaoSONG aiChaoSONG changed the title schedule: fix address space mismatches [skip ci]schedule: fix address space mismatches Mar 17, 2023
@aiChaoSONG aiChaoSONG force-pushed the sparse-fix branch 2 times, most recently from 275d695 to ff8e074 Compare March 17, 2023 05:01
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>
@aiChaoSONG aiChaoSONG changed the title [skip ci]schedule: fix address space mismatches schedule: fix address space mismatches Mar 17, 2023
@lgirdwood lgirdwood merged commit 34ea694 into thesofproject:main Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants