secret-hiding: Add apply_kernel_patches.sh #5637
Merged
+52
−0
Conversation
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
For kernel development, it's handy to have a Git tree with all these patches applied. However since the existing source of truth is these patch files, instead of directly providing such a tree, it's simpler to just provide a script that generates one. The user needs to run it from a kernel tree checked out at a specific revision, but they don't need to know that, they can just run it and it will tell them. Signed-off-by: Brendan Jackman <[email protected]>
kalyazin
approved these changes
Jan 19, 2026
JackThomson2
approved these changes
Jan 19, 2026
JackThomson2
merged commit 4c8085a
into
firecracker-microvm:feature/secret-hiding
5 checks passed
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.
For kernel development, it's handy to have a Git tree with all these patches applied. However since the existing source of truth is these patch files, instead of directly providing such a tree, it's simpler to just provide a script that generates one.
The user needs to run it from a kernel tree checked out at a specific revision, but they don't need to know that, they can just run it and it will tell them.
Changes
...
Reason
...
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.PR Checklist
I have read and understand CONTRIBUTING.md.
I have run
tools/devtool checkbuild --allto verify that the PR passesbuild checks on all supported architectures.
( Don't have Docker, doesn't seem relevant to this PR)
I have run
tools/devtool checkstyleto verify that the PR passes theautomated style checks
( Don't have Docker, doesn't seem relevant to this PR)
I have described what is done in these changes, why they are needed, and
how they are solving the problem in a clear and encompassing way.
I have updated any relevant documentation (both in code and in the docs)
in the PR.
I have mentioned all user-facing changes in
CHANGELOG.md.If a specific issue led to this PR, this PR closes the issue.
When making API changes, I have followed the
Runbook for Firecracker API changes.
I have tested all new and changed functionalities in unit tests and/or
integration tests.
I have linked an issue to every new
TODO.rust-vmm.