chore(deps): update dependency kernel-rt-7.2 to v7.2.6 - #179
Merged
Merged
Conversation
![renovate-hash-sync[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
Recomputed from a freshly-fetched artifact:
- driver/firmware/libchdr package pins: sha256sum of the github
archive tarball at the new pinned owner/repo/ref (same "locally
computed" practice this tree's own .hash file headers already
document)
- kernel pins (stable 6.18.y and the RT/beta 7.2 line): kernel.org's
signed sha256sums.asc for each pin's own vN.x series. An -rc is
never refreshed here -- no signed manifest exists for one
- ip7z/7zip pins (lzma-sdk, 7zip): sha256sum of the release
ASSET for the new version (upstream publishes no checksums at
all -- see package/lzma-sdk/lzma-sdk.hash's header), PLUS the
files each package's *_LICENSE_FILES names, hashed from that
same asset. A changed license file is refreshed AND diffed
into the step log with a ::warning:: -- read that diff before
merging; it is the only thing standing between an automated
hash refresh and a silent relicense
- sdcard payload pins (update_all.sh, wifi.sh): sha256 + size of
the raw file at the new pinned commit, rewritten in place in
scripts/fetch-sdcard-payload.sh
- Buildroot pin (BUILDROOT_SHA256, root Makefile): transcribed
from buildroot.org's GPG-signed release manifest
(buildroot-<ver>.tar.gz.sign) -- the same signed file `make
buildroot-showsig` prints, never a locally-computed sha256sum
of the tarball (that remains forbidden; see the Makefile's own
header comment)
- azcopy pin: REBUILT, not fetched. Buildroot's own
support/download/go-post-process re-ran `go mod vendor` over the
newly pinned tag with the Go version the pinned Buildroot tree
pins, and the resulting azcopy-<ver>-go2.tar.gz was hashed --
the only way this value can be derived, since no URL serves that
file (see package/azcopy/azcopy.hash's header). LICENSE and
NOTICE.txt were re-hashed from the same tarball
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
mcfbytes
added a commit
that referenced
this pull request
Sep 15, 2026
6.18.52 and 7.2.6 both carry the stable fix that deletes
ctlr->imu_timestamp_us += 1000 * ctlr->imu_avg_delta_ms;
from joycon_parse_imu_report(). That line was leading context in
0032's hid_warn_ratelimited -> hid_dbg hunk, so the hunk failed at
`patch -F0` on both Renovate bumps and took the whole build with it
(runs 34904210029 / PR #178, 34904230953 / PR #179).
The hunk's leading context is now the single
if (dropped_pkts > JC_IMU_DROPPED_PKT_WARNING) {
line, which reads the same before and after that fix. It has to: the
patch is one real file symlinked into linux-patches-beta/ and
de25nano/linux-patches/, and those pins move on separate Renovate
managers (6.18 vs kernel-rt-7.2), so a single copy must apply to both
the old and the new tree or whichever board is still on the old pin
breaks instead.
Verified by replaying each full series at Buildroot's own flags
(patch -F0 -g0 -p1 --no-backup-if-mismatch -t -N) against trees built
from the pinned tarballs plus the kernel.org incremental patches:
6.18.51 de10nano 38 patches 0 failed 13 offsets 0 fuzz
6.18.52 de10nano 38 patches 0 failed 19 offsets 0 fuzz
7.2.5 beta/RT 40 patches 0 failed 71 offsets 0 fuzz
7.2.6 beta/RT 40 patches 0 failed 74 offsets 0 fuzz
7.2.5 de25nano 34 patches 0 failed 68 offsets 0 fuzz
7.2.6 de25nano 34 patches 0 failed 71 offsets 0 fuzz
Offsets only, zero fuzz -- the standard docs/kernel-export.md already
records for this series. 0032 was the only failure on the bumped trees,
so nothing was hidden behind it. Output on the two current pins is
byte-identical to the pre-trim patch, and `git am` replay of all six
combinations is clean, so the export path is unaffected.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SCbqKSYnSe7R5WGFT6w4Rm
mcfbytes
added a commit
that referenced
this pull request
Sep 16, 2026
6.18.52 and 7.2.6 both carry the stable fix that deletes
ctlr->imu_timestamp_us += 1000 * ctlr->imu_avg_delta_ms;
from joycon_parse_imu_report(). That line was leading context in
0032's hid_warn_ratelimited -> hid_dbg hunk, so the hunk failed at
`patch -F0` on both Renovate bumps and took the whole build with it
(runs 34904210029 / PR #178, 34904230953 / PR #179).
The hunk's leading context is now the single
if (dropped_pkts > JC_IMU_DROPPED_PKT_WARNING) {
line, which reads the same before and after that fix. It has to: the
patch is one real file symlinked into linux-patches-beta/ and
de25nano/linux-patches/, and those pins move on separate Renovate
managers (6.18 vs kernel-rt-7.2), so a single copy must apply to both
the old and the new tree or whichever board is still on the old pin
breaks instead.
Verified by replaying each full series at Buildroot's own flags
(patch -F0 -g0 -p1 --no-backup-if-mismatch -t -N) against trees built
from the pinned tarballs plus the kernel.org incremental patches:
6.18.51 de10nano 38 patches 0 failed 13 offsets 0 fuzz
6.18.52 de10nano 38 patches 0 failed 19 offsets 0 fuzz
7.2.5 beta/RT 40 patches 0 failed 71 offsets 0 fuzz
7.2.6 beta/RT 40 patches 0 failed 74 offsets 0 fuzz
7.2.5 de25nano 34 patches 0 failed 68 offsets 0 fuzz
7.2.6 de25nano 34 patches 0 failed 71 offsets 0 fuzz
Offsets only, zero fuzz -- the standard docs/kernel-export.md already
records for this series. 0032 was the only failure on the bumped trees,
so nothing was hidden behind it. Output on the two current pins is
byte-identical to the pre-trim patch, and `git am` replay of all six
combinations is clean, so the export path is unaffected.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SCbqKSYnSe7R5WGFT6w4Rm
mcfbytes
added a commit
that referenced
this pull request
Sep 16, 2026
chore(deps): update dependency kernel-rt-7.2 to v7.2.6
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
1 participant
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.
This PR contains the following updates:
7.2.5→7.2.6Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.