doc: CHANGELOG entry for v6.2.3#295
Merged
Merged
Conversation
Summarize the v6.2.3 patch release (PR #291: S3C_CPU paths gated on CONFIG_SOO, fixing the non-SOO AVZ boot stalls and lcdifv3 timeout storms on verdin-imx8mp) and add the CHANGELOG to the after-tagging checklist of the release process so it stops drifting — it had not been touched since v2021.4.1.
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
1 participant
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.
Adds the missing
CHANGELOGentry for the v6.2.3 patch release (#291: S3C_CPU paths gated onCONFIG_SOO, fixing the non-SOO AVZ boot stalls and lcdifv3 timeout storms on verdin-imx8mp), in the file's existing format.Also adds the
CHANGELOGto the After tagging checklist introduced by #294 — the file had not been touched since v2021.4.1, same silent-drift problem as the README table.Note: the gap between v2021.4.1 and v6.2.3 remains; backfilling the 5.4/6.1/6.2.0-6.2.2 entries from the GitHub Release notes is possible as a follow-up if wanted.