Don't set CONFIG_FRAME_WARN in flavor configs#88
Merged
Conversation
Contributor
|
We can drop this. |
kaniini
approved these changes
Jun 3, 2025
azenla
approved these changes
Jun 3, 2025
azenla
left a comment
azenla
left a comment
Member
There was a problem hiding this comment.
The config was originally derived from alpine, so I suspect that might be related to why this was like this
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
3 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.
We have been setting
CONFIG_FRAME_WARN=1024in zone/host configs.This is not set in default upstream kconfigs. Setting it causes (some) kernel builds to fail (i.e. it's not us, it's upstream's code - specifically the
amdgpudriver in ~some versions).openpaxvariants, specifically?cc @kaniini