CLK 6.12 Update branding in package descrptions and log messages#1122
Merged
bmastbergen merged 2 commits intociq-6.12.yfrom Apr 23, 2026
Merged
CLK 6.12 Update branding in package descrptions and log messages#1122bmastbergen merged 2 commits intociq-6.12.yfrom
bmastbergen merged 2 commits intociq-6.12.yfrom
Conversation
roxanan1996
approved these changes
Apr 23, 2026
shreeya-patel98
approved these changes
Apr 23, 2026
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
4 participants
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.
Just little cleanup to fix some branding in the spec where a customer might actually see it. There is certainly more cleanup to be done here in the areas that customers don't see which we can do in the future. This PR also adds an RPM build workflow so that spec changes are validated to at least build successfully for both x86_64 and aarch64. This workflow is essentially the same build steps I do before creating a secure boot ticket for CLK kernels, so this helps ensure we are in good shape for releases.