Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Backport release-24.11] Kernel updates for 2025-01-09 #372446

Merged
merged 4 commits into from
Jan 9, 2025
Merged

[Backport release-24.11] Kernel updates for 2025-01-09 #372446

merged 4 commits into from
Jan 9, 2025

Conversation

nix-backports[bot]
Copy link

@nix-backports nix-backports bot commented Jan 9, 2025

Bot-based backport to release-24.11, triggered by a label in #372387.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-commiter, if you find that it is not acceptable, leave a comment.

@GaetanLepage @github-actions
linux_testing: 6.13-rc5 -> 6.13-rc6
9d301a9 
(cherry picked from commit 66e0b80)
@GaetanLepage @github-actions
linux_6_12: 6.12.8 -> 6.12.9
965a721 
(cherry picked from commit d580ebd)
@GaetanLepage @github-actions
linux_6_6: 6.6.69 -> 6.6.70
0312d89 
(cherry picked from commit ea1792a)
@GaetanLepage @github-actions
linux_6_1: 6.1.123 -> 6.1.124
3af7f16 
(cherry picked from commit 9184260)
@nix-backports nix-backports bot mentioned this pull request Jan 9, 2025
Merged
13 tasks
@github-actions github-actions bot added the 6.topic: kernel The Linux kernel label Jan 9, 2025
@fabianhjr fabianhjr merged commit 8bf5222 into release-24.11 Jan 9, 2025
17 of 21 checks passed
@fabianhjr fabianhjr deleted the backport-372387-to-release-24.11 branch January 9, 2025 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
6.topic: kernel The Linux kernel 10.rebuild-darwin: 1-10 10.rebuild-linux: 1001-2500
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@fabianhjr @GaetanLepage