Make kernel version to generate headers for configurable in CI#17
Merged
danielocfb merged 1 commit intolibbpf:mainfrom Jan 29, 2026
Merged
Conversation
Make the kernel version to generate headers for configurable when triggered from the UI. Because Actions are stupid, we can't introduce a constant and have to hardcode the default twice -- at least if we want users to see what version to generate for by default. So at least make sure to keep the definition in the same file by not making it an input to the workflow_call event as well. Signed-off-by: Daniel Müller <deso@posteo.net>
Contributor
Author
|
Tested here:
|
Contributor
Author
|
We can refine this some more subsequently. |
theihor
approved these changes
Jan 29, 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
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.
Make the kernel version to generate headers for configurable when triggered from the UI. Because Actions are stupid, we can't introduce a constant and have to hardcode the default twice -- at least if we want users to see what version to generate for by default. So at least make sure to keep the definition in the same file by not making it an input to the workflow_call event as well.