Repository navigation
waves: avoid calling MaxxEffect_Message before MaxxEffect_Initialize - #9882
Merged
Merged
Conversation
barry-waves
commented
Mar 10, 2025
barry-waves
commented
Contributor
barry-waves
requested review from
dbaluta,
kv2019i,
lbetlej,
lgirdwood,
mmaka1 and
plbossart
as code owners
March 10, 2025 11:36
lgirdwood
approved these changes
Mar 10, 2025
johnylin76
reviewed
Mar 10, 2025
Save the blob into the cache and ensure that MaxxEffect_Message
is not called before MaxxEffect_Initialize to avoid returning
an error code from MaxxEffect_Message.
Signed-off-by: barry.jan <barry.jan@waves.com>
johnylin76
approved these changes
Mar 11, 2025
Contributor
|
LGTM. |
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
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.
