Repository navigation
Add patches for 7.2 - #2262
Closed
fildunsky wants to merge 1 commit into
Closed
Add patches for 7.2#2262fildunsky wants to merge 1 commit into
fildunsky wants to merge 1 commit into
Conversation
Forward-ported from the 7.1 series in PR linux-surface#2178. Applied in order with git am --3way against v7.2.2, fourteen of the fifteen patches land with no conflict at all. The exception is 0011-surface-shutdown.patch, and only in context: in include/linux/pci.h the comment on the neighbouring non_mappable_bars field was reworded from "BARs can't be mapped to user-space" to "BARs can't be mapped by CPU or peers". The line the patch adds and the code around it are unchanged. Updated the context so the patch applies with zero fuzz. configs/surface-7.2.config is surface-7.1.config unchanged; nothing in it needed adjusting for 7.2. Built and running on a Surface Pro 8 as 7.2.2-surface-1: touch (ithc), pen, all three cameras including the IR one, face authentication, suspend and battery all work. Base config was Ubuntu's shipped config-7.0.0-30-generic merged with pkg/debian/kernel/ubuntu.config and this config. CONFIG_RUST comes out unset, as it does for the existing series - DEBUG_INFO_NONE leaves no GENDWARFKSYMS, so Kconfig does not offer it.
This was referenced Sep 1, 2026
Open
Author
|
Closing this as a duplicate: #2233 already carries the 7.2 series, opened on For what it is worth, the two were produced independently and come out the The Pro 8 test results and the build notes from this description are now on |
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
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.
Forward-ported from the 7.1 series in #2178 — the work there is @Apiznel's, this
only carries it to 7.2.
Fourteen of the fifteen patches apply to v7.2.2 unchanged (
git am --3way, noconflicts, nothing to resolve).
Rebased
0011-surface-shutdown.patchbecause of:That commit reworded the comment on the neighbouring
non_mappable_barsfieldin
include/linux/pci.h, from "BARs can't be mapped to user-space" to "BARscan't be mapped by CPU or peers". Context only — the line the patch adds and the
code around it are unchanged. Updated so it applies with zero fuzz and zero
offset.
configs/surface-7.2.configissurface-7.1.configunchanged; nothing in itneeded adjusting.
Tested
Built as
7.2.2-surface-1and running on a Surface Pro 8: touch (ithc),pen, suspend, battery, and all three cameras including the IR one with face
authentication through PAM.
Base config was Ubuntu's shipped
config-7.0.0-30-genericmerged withpkg/debian/kernel/ubuntu.configand this config, following.github/scripts/package/debian.sh.CONFIG_RUSTcomes out unset, as it doesfor the existing series —
ubuntu.configsetsDEBUG_INFO_NONE, which leavesno
GENDWARFKSYMS, so Kconfig does not offer it withMODVERSIONSon.Only the Pro 8 is covered by that testing; the rest of the series is carried
across unchanged from #2178 and is as tested as it was there.
Note on ordering
This does not depend on #2178 landing —
patches/7.2/is a new directory andtouches nothing else. If #2178 is merged first there is no conflict either.