Uh oh!
There was an error while loading. Please reload this page.
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.
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.
@lgirdwood@jajanusz It really would be better to do the kernel PRs at the same time and have the person doing the change write a git commit message that explains the change. This "late-bound" sync of changes to kernel is not fun. Thanks for @xiulipan doing the patch, but I again have to ask for some improvements to the commit message:
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.
agree with @kv2019i , this is a complete fail of the ABI change process.
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.
The kernel and FW PRs must be done together and mention each other. It is up to maintainers to label as ABI and then to align both PRs using the classifier. So this is several steps taken by at least 3 people and is not being fully processed by everybody.
I am now wondering whether we should now be moving to a ABI minor bump only for every FW release (when the regular FW releases start soon). This would allow the kernel team to plan each merge window in advance to a specific FW version. @lbetlej fyi - regular FW releases would help here.
There is also complexity about bumping ABI in relation to kernel releases and FW releases. i.e. when do we close the ABI minor merge window for new kernel and FW releases (and use the next minor).