[PATCH v2] test: dmafwd: reorder cache size calculations #1918
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
odpbuild
changed the title
MatiasElo
approved these changes
Sep 29, 2023
Move pool and stash cache calculations inside branches where related logic resides, preventing uninitialized value usage. The actual uninitialized usage is prevented later and does not cause any runtime issues. Nevertheless, this is now properly handled during startup. Signed-off-by: Tuomas Taipale <tuomas.taipale@nokia.com> Reviewed-by: Matias Elo <matias.elo@nokia.com>
TuomasTaipale
force-pushed
the
dev/dmafwd
branch
from
f3c711e
to
95cc30d
Compare
odpbuild
changed the title
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.
Move pool and stash cache calculations inside branches where related logic resides, preventing uninitialized value usage. The actual uninitialized usage is prevented later and does not cause any runtime issues. Nevertheless, this is now properly handled during startup.
v2: