Skip to content

kernel updates for 2026-03-19#501448

Merged
vcunat merged 3 commits intoNixOS:staging-nextfrom
qowoz:kernels
Mar 20, 2026
Merged

kernel updates for 2026-03-19#501448
vcunat merged 3 commits intoNixOS:staging-nextfrom
qowoz:kernels

Conversation

@zowoq
Copy link
Contributor

@zowoq zowoq commented Mar 19, 2026 •
edited
Loading

Things done

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

cc @NixOS/linux-kernel @vcunat

@zowoq zowoq added the backport release-25.11 Backport PR automatically label Mar 19, 2026
@zowoq zowoq changed the title Kernels kernel updates for 2026-03-19 Mar 19, 2026
@zowoq zowoq mentioned this pull request Mar 19, 2026
Merged
@zowoq
Copy link
Contributor Author

zowoq commented Mar 19, 2026

I'll leave this as a draft until #501226 (comment) is answered.

@nixpkgs-ci nixpkgs-ci bot added 8.has: package (update) This PR updates a package to a newer version 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 501-1000 This PR causes many rebuilds on Linux and should normally target the staging branches. 6.topic: kernel The Linux kernel labels Mar 19, 2026
@vcunat vcunat changed the base branch from staging-nixos to staging-next March 20, 2026 05:22
@vcunat vcunat marked this pull request as ready for review March 20, 2026 05:22
@nixpkgs-ci nixpkgs-ci bot closed this Mar 20, 2026
@nixpkgs-ci nixpkgs-ci bot reopened this Mar 20, 2026
@nixpkgs-ci nixpkgs-ci bot requested a review from a team March 20, 2026 05:31
@vcunat vcunat added this pull request to the merge queue Mar 20, 2026
@vcunat
Copy link
Member

vcunat commented Mar 20, 2026

I built linux_6_18 linux_6_19 for x86_64-linux.

Merged via the queue into NixOS:staging-next with commit 35d5554 Mar 20, 2026
59 of 63 checks passed
@nixpkgs-ci
Copy link
Contributor

nixpkgs-ci bot commented Mar 20, 2026

Backport failed for release-25.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-25.11
git worktree add -d .worktree/backport-501448-to-release-25.11 origin/release-25.11
cd .worktree/backport-501448-to-release-25.11
git switch --create backport-501448-to-release-25.11
git cherry-pick -x 10628e4b8a226f98bdd8f0eec92e03bc5281f592 64b68b63e60b60084dab3ad5c8fa8852b230b899 a815e4136b006acc484b836f4970dafc1674a354

@zowoq zowoq removed the backport release-25.11 Backport PR automatically label Mar 20, 2026
@zowoq zowoq deleted the kernels branch March 20, 2026 06:57
@zowoq zowoq added the 8.has: port to stable This PR already has a backport to the stable release. label Mar 20, 2026
@zowoq
Copy link
Contributor Author

zowoq commented Mar 20, 2026

Backports included in #501542

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 8.has: package (update) This PR updates a package to a newer version 8.has: port to stable This PR already has a backport to the stable release. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-linux: 501-1000 This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@zowoq @vcunat