Linux kernel regression status

[next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive]

(v7.2-rc1)

mt76 newly rejects formerly working MAC from EPROM by Tobias Klausmann

Earliest & latest activity: & . Noteworthy: [1], [2], [resolution], [is a duplicate].

[1]: Re: [PATCH wireless-next] wifi: mt76: fix MAC address for non OF pcie cards [implicit due to Link/Closes tag]

, by Thorsten Leemhuis (monitored)

[2]: [PATCHv2 wireless] wifi: mt76: fix MAC address for non OF pcie cards [implicit due to Link/Closes tag]

, by Rosen Penev (monitored)

Resolution: 7fd35e8c0548 ("wifi: mt76: fix MAC address for non OF pcie cards")

in v7.2-rc5

Latest five known activities:

Commit 7fd35e8c0548 in mainline
, by Rosen Penev
7fd35e8c0548, the fix specified through '#regzbot fix:' earlier landed in mainline
, by Rosen Penev
Commit 7fd35e8c0548 in next
, by Rosen Penev
[PATCHv2 wireless] wifi: mt76: fix MAC address for non OF pcie cards
, by Rosen Penev; contains a signed-off patch
Re: [PATCH wireless-next] wifi: mt76: fix MAC address for non OF pcie cards
, by Tobias Klausmann

Regzbot command history:

fix: 7fd35e8c0548 [implicit, due to a Link/Closes tag]
, by Rosen Penev
fixed: 'fix' commit '7fd35e8c0548' now in 'mainline'
, by Rosen Penev
fix: 7fd35e8c0548 in next referred to this regression
, by Rosen Penev
relate: https://lore.kernel.org/lkml/20260706232857.807044-1-rosenp@gmail.com/ [PATCHv2 wireless] wifi: mt76: fix MAC address for non OF pcie cards [implicit due to Link/Closes tag]
, by Rosen Penev
relate: https://lore.kernel.org/lkml/036cc81d-115a-4c0e-9542-71ed2ee04e9b@leemhuis.info/ Re: [PATCH wireless-next] wifi: mt76: fix MAC address for non OF pcie cards [implicit due to Link/Closes tag]
, by Thorsten Leemhuis
duplicate: https://lore.kernel.org/lkml/ajRmlyx_AEGybykL@soda.int.kasm.eu/ [implicit via duplicate]
, by Thorsten Leemhuis
introduced: 31ee1582717e22 [implicit via duplicate]
, by Thorsten Leemhuis

mainline

[compiled by regzbot on 2026-10-12 17:08:35 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

[recently 113 events occurred that regzbot was unable to handle]