Fix build on 6.12.101 and later in the 6.12 series - #209
Merged
Conversation
set_monitor_channel gained a struct net_device *dev argument in 9c4f83092775 (6.13), and 6.12 stable took it at 6.12.101. The 6.13.0 gate therefore misses 6.12.101 to the end of the 6.12 series. 6.13 and newer were never affected. 6.13.0 sorts above 6.12.101, so the single check covers both.
Lucid-Duck
force-pushed
the
set-monitor-channel-6.12.101
branch
from
August 18, 2026 23:31
c8a3911 to
cf03ca2
Compare
Lucid-Duck
changed the title
Owner
|
Thank you very much. |
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
2 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.
@morrownr As offered.
set_monitor_channelgained astruct net_device *devargument in 9c4f83092775, which is 6.13. 6.12 stable took it at 6.12.101 as a dependency of an unrelated deadlock fix, so the 6.13.0 gate misses that window. 6.13 and newer were never affected.Built both ways against 6.12.100 and 6.12.101 from kernel.org: stock fails on 6.12.101 only, at
.set_monitor_channel = cfg80211_rtw_set_monitor_channel, and this clears it without touching 6.12.100.6.12.101 is the exact boundary: 6.12.103, 6.18.44 and 7.1.8 take the new argument, 6.6.151, 6.1.182, 5.15.215 and 5.10.264 do not. 6.13.0 sorts above 6.12.101, so the one check covers both.
#208 has the same one-line change with 6.12.0, which is too wide and breaks 6.12.0 through 6.12.100.