Linux kernel regression status

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


next
none known by regzbot

mainline
  • 3aadf100f93d
    (v6.9-rc5)
  • Re: [PATCH] Revert "vmgenid: emit uevent when VMGENID updates" by Alexander Graf

    All known activities:

    Regzbot command history:

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

  • 86211eea8ae1
    (v6.9-rc1)
  • btrfs: snapper fails by Linux regression tracking (Thorsten Leemhuis)
    [1]: [PATCH] btrfs: qgroup: do not check qgroup inherit if qgroup is disabled
    , by Qu Wenruo (monitored)

    All known activities:

    Regzbot command history:

  • a8b5d4809b50
    (v6.9-rc2)
  • net: wifi: iwlwifi: Thinkpad 480 no Wifi by Stefan Seyfried
    [1]: [PATCH] wifi: iwlwifi: mvm: fix link ID management
    , by Johannes Berg (monitored)

    Latest five known activities:

    Regzbot command history:

  • 073237281a50
    (v6.9-rc1)
  • ACPI: PM: s2idle: sleep broken on 13th Gen Lenovo laptops by Mark Pearson

    Latest five known activities:

    Regzbot command history:

  • v5.19.17..v6.0.0-rc1
  • sk_memory_allocated counter leaking on aarch64 by Jonathan HeathcoteLatest patch: [PATCH net] net: fix sk_memory_allocated_{add|sub} vs softirqs
    , by Eric Dumazet; signed-off-by present
    Earlier patches: 1, 2

    Latest five known activities:

    Regzbot command history:

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:


    stable/longterm
  • 6083089ab006
    (v6.1.83)
  • Bluetooth kernel BUG with Intel AX211 by Jeremy Lainé and Paul Menzel

    Latest five known activities:

    Regzbot command history:

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:


    [compiled by regzbot on 2024-04-25 08:40:04 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

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