Bump to latest 6.18 LTS patch release

.github/workflows/check-kernel-release.yml

@@ -15,12 +15,17 @@ jobs:
         uses: actions/checkout@v6
         with:
           fetch-depth: 0
-          token: ${{ secrets.KERNEL_UPDATE_TOKEN }}
+          persist-credentials: false
 
       - name: Fetch kernel.org and check for 6.18 release
         id: check
         run: |
           set -e -o pipefail
+          if ! gh api user --silent; then
+            echo "::error::KERNEL_UPDATE_TOKEN was rejected, it has likely expired and must be regenerated"
+            exit 1
+          fi
+
           # Fetch the kernel.org frontpage and extract 6.18 version
           CURRENT_VERSION=$(curl -s https://www.kernel.org/ | grep -oP '6\.18\.\d+' | head -n1)
 

configs/aarch64_defconfig

@@ -26,7 +26,7 @@ BR2_ROOTFS_OVERLAY="${BR2_EXTERNAL_INFIX_PATH}/board/common/rootfs ${BR2_EXTERNA
 BR2_ROOTFS_POST_BUILD_SCRIPT="${BR2_EXTERNAL_INFIX_PATH}/board/common/post-build.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.59"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.60"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="${BR2_EXTERNAL_INFIX_PATH}/board/aarch64/linux_defconfig"
 BR2_LINUX_KERNEL_INSTALL_TARGET=y

configs/aarch64_minimal_defconfig

@@ -26,7 +26,7 @@ BR2_ROOTFS_OVERLAY="${BR2_EXTERNAL_INFIX_PATH}/board/common/rootfs ${BR2_EXTERNA
 BR2_ROOTFS_POST_BUILD_SCRIPT="${BR2_EXTERNAL_INFIX_PATH}/board/common/post-build.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.59"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.60"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="${BR2_EXTERNAL_INFIX_PATH}/board/aarch64/linux_defconfig"
 BR2_LINUX_KERNEL_INSTALL_TARGET=y

configs/arm_defconfig

@@ -28,7 +28,7 @@ BR2_ROOTFS_OVERLAY="${BR2_EXTERNAL_INFIX_PATH}/board/common/rootfs ${BR2_EXTERNA
 BR2_ROOTFS_POST_BUILD_SCRIPT="${BR2_EXTERNAL_INFIX_PATH}/board/common/post-build.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.59"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.60"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="${BR2_EXTERNAL_INFIX_PATH}/board/arm/linux_defconfig"
 BR2_LINUX_KERNEL_INSTALL_TARGET=y

configs/arm_minimal_defconfig

@@ -28,7 +28,7 @@ BR2_ROOTFS_OVERLAY="${BR2_EXTERNAL_INFIX_PATH}/board/common/rootfs ${BR2_EXTERNA
 BR2_ROOTFS_POST_BUILD_SCRIPT="${BR2_EXTERNAL_INFIX_PATH}/board/common/post-build.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.59"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.60"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="${BR2_EXTERNAL_INFIX_PATH}/board/arm/linux_defconfig"
 BR2_LINUX_KERNEL_INSTALL_TARGET=y

configs/riscv64_defconfig

@@ -25,7 +25,7 @@ BR2_ROOTFS_OVERLAY="${BR2_EXTERNAL_INFIX_PATH}/board/common/rootfs ${BR2_EXTERNA
 BR2_ROOTFS_POST_BUILD_SCRIPT="${BR2_EXTERNAL_INFIX_PATH}/board/common/post-build.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.59"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.60"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="${BR2_EXTERNAL_INFIX_PATH}/board/riscv64/linux_defconfig"
 BR2_LINUX_KERNEL_INSTALL_TARGET=y

configs/x86_64_defconfig

@@ -25,7 +25,7 @@ BR2_ROOTFS_OVERLAY="${BR2_EXTERNAL_INFIX_PATH}/board/common/rootfs ${BR2_EXTERNA
 BR2_ROOTFS_POST_BUILD_SCRIPT="board/qemu/x86_64/post-build.sh ${BR2_EXTERNAL_INFIX_PATH}/board/common/post-build.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.59"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.60"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="${BR2_EXTERNAL_INFIX_PATH}/board/x86_64/linux_defconfig"
 BR2_LINUX_KERNEL_INSTALL_TARGET=y

configs/x86_64_minimal_defconfig

@@ -25,7 +25,7 @@ BR2_ROOTFS_OVERLAY="${BR2_EXTERNAL_INFIX_PATH}/board/common/rootfs ${BR2_EXTERNA
 BR2_ROOTFS_POST_BUILD_SCRIPT="board/qemu/x86_64/post-build.sh ${BR2_EXTERNAL_INFIX_PATH}/board/common/post-build.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.59"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.60"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="${BR2_EXTERNAL_INFIX_PATH}/board/x86_64/linux_defconfig"
 BR2_LINUX_KERNEL_INSTALL_TARGET=y

doc/ChangeLog.md

@@ -20,7 +20,7 @@ All notable changes to the project are documented in this file.
 
 ### Changes
 
-- Upgrade Linux kernel to 6.18.59 (LTS)
+- Upgrade Linux kernel to 6.18.60 (LTS)
 - Upgrade libyang to 6.4.13, sysrepo to 5.2.27, libnetconf2 to 4.6.4,
   netopeer2 to 2.8.21, and rousette to the latest development version
 - Operational data is returned much faster, from the CLI, NETCONF,

patches/linux/6.18.59/0001-net-phy-marvell10g-Support-firmware-loading-on-88X33.patch → patches/linux/6.18.60/0001-net-phy-marvell10g-Support-firmware-loading-on-88X33.patch

@@ -1,8 +1,9 @@
-From be9e488785558be53772aebbed94ec31a7e4e016 Mon Sep 17 00:00:00 2001
+From 94ac144a9d46ca99606a6b39533e3fb9686fe70f Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 19 Sep 2023 18:38:10 +0200
-Subject: [PATCH 001/133] net: phy: marvell10g: Support firmware loading on
+Subject: [PATCH 001/139] net: phy: marvell10g: Support firmware loading on
  88X3310
+Organization: Wires
 
 When probing, if a device is waiting for firmware to be loaded into
 its RAM, ask userspace for the binary and load it over XMDIO.

patches/linux/6.18.59/0002-net-phy-marvell10g-Fix-power-up-when-strapped-to-sta.patch → patches/linux/6.18.60/0002-net-phy-marvell10g-Fix-power-up-when-strapped-to-sta.patch

@@ -1,8 +1,9 @@
-From ab97ae60afb006052e5fa064fc505027bd5e05e9 Mon Sep 17 00:00:00 2001
+From 8f9d687af40bb456176fc312e57c9cfbdef5a179 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 21 Nov 2023 20:15:24 +0100
-Subject: [PATCH 002/133] net: phy: marvell10g: Fix power-up when strapped to
+Subject: [PATCH 002/139] net: phy: marvell10g: Fix power-up when strapped to
  start powered down
+Organization: Wires
 
 On devices which are hardware strapped to start powered down (PDSTATE
 == 1), make sure that we clear the power-down bit on all units

patches/linux/6.18.59/0003-net-phy-marvell10g-Add-LED-support-for-88X3310.patch → patches/linux/6.18.60/0003-net-phy-marvell10g-Add-LED-support-for-88X3310.patch

@@ -1,7 +1,8 @@
-From 743bb6420fa7f0061d6980f4c944a1e377ab384c Mon Sep 17 00:00:00 2001
+From 45f6495270b4268d0d42cf21a72b64b90111bb47 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 15 Nov 2023 20:58:42 +0100
-Subject: [PATCH 003/133] net: phy: marvell10g: Add LED support for 88X3310
+Subject: [PATCH 003/139] net: phy: marvell10g: Add LED support for 88X3310
+Organization: Wires
 
 Pickup the LEDs from the state in which the hardware reset or
 bootloader left them, but also support further configuration via

patches/linux/6.18.59/0004-net-phy-marvell10g-Support-LEDs-tied-to-a-single-med.patch → patches/linux/6.18.60/0004-net-phy-marvell10g-Support-LEDs-tied-to-a-single-med.patch

@@ -1,8 +1,9 @@
-From 7ac5820cb66bb4660e48bd2482c2ecfec73472a7 Mon Sep 17 00:00:00 2001
+From f1119c42028634fcbb4be756c0ab8ab3d97e01c3 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 12 Dec 2023 09:51:05 +0100
-Subject: [PATCH 004/133] net: phy: marvell10g: Support LEDs tied to a single
+Subject: [PATCH 004/139] net: phy: marvell10g: Support LEDs tied to a single
  media side
+Organization: Wires
 
 In a combo-port setup, i.e. where both the copper and fiber interface
 are available to the user, the LEDs may be physically located either

patches/linux/6.18.59/0005-net-phy-Do-not-resume-PHY-when-attaching.patch → patches/linux/6.18.60/0005-net-phy-Do-not-resume-PHY-when-attaching.patch

@@ -1,7 +1,8 @@
-From 7e8ada27f783e13ceb7d241af6c66cda952005d8 Mon Sep 17 00:00:00 2001
+From 5c358b5de8e20087d10f58e5323bd2b7f7a86656 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 27 Mar 2024 10:10:19 +0100
-Subject: [PATCH 005/133] net: phy: Do not resume PHY when attaching
+Subject: [PATCH 005/139] net: phy: Do not resume PHY when attaching
+Organization: Wires
 
 The PHY should not start negotiating with its link-partner until
 explicitly instructed to do so.

patches/linux/6.18.59/0006-net-bridge-avoid-classifying-unknown-multicast-as-mr.patch → patches/linux/6.18.60/0006-net-bridge-avoid-classifying-unknown-multicast-as-mr.patch

@@ -1,8 +1,9 @@
-From 172e50a493fbcee1d040f321dd8a5508de413755 Mon Sep 17 00:00:00 2001
+From bd0dcbe1889268b6e313c626ad7f9cee9122a7d6 Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Mon, 4 Mar 2024 16:47:28 +0100
-Subject: [PATCH 006/133] net: bridge: avoid classifying unknown multicast as
+Subject: [PATCH 006/139] net: bridge: avoid classifying unknown multicast as
  mrouters_only
+Organization: Wires
 
 Unknown multicast, MAC/IPv4/IPv6, should always be flooded according to
 the per-port mcast_flood setting, as well as to detected and configured

patches/linux/6.18.59/0007-net-bridge-Ignore-router-ports-when-forwarding-L2-mu.patch → patches/linux/6.18.60/0007-net-bridge-Ignore-router-ports-when-forwarding-L2-mu.patch

@@ -1,8 +1,9 @@
-From dceaee463f2db31705b4a65b33ce029dab57ec05 Mon Sep 17 00:00:00 2001
+From 8faaf6a9fd22020a005f68ead86e8d6ae05ba39e Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Tue, 5 Mar 2024 06:44:41 +0100
-Subject: [PATCH 007/133] net: bridge: Ignore router ports when forwarding L2
+Subject: [PATCH 007/139] net: bridge: Ignore router ports when forwarding L2
  multicast
+Organization: Wires
 
 Multicast router ports are either statically configured or learned from
 control protocol traffic (IGMP/MLD/PIM).  These protocols regulate IP

patches/linux/6.18.59/0008-net-bridge-drop-delay-for-applying-strict-multicast-.patch → patches/linux/6.18.60/0008-net-bridge-drop-delay-for-applying-strict-multicast-.patch

@@ -1,8 +1,9 @@
-From b03081e706b0116e1cbca21fe51b956589a3c347 Mon Sep 17 00:00:00 2001
+From fac83a3c9eac17b8372ff21cc6bed004aea571b4 Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Thu, 4 Apr 2024 16:36:30 +0200
-Subject: [PATCH 008/133] net: bridge: drop delay for applying strict multicast
+Subject: [PATCH 008/139] net: bridge: drop delay for applying strict multicast
  filtering
+Organization: Wires
 
 This *local* patch drops the initial delay before applying strict multicast
 filtering, introduced in [1] and recently updated in [2].

patches/linux/6.18.59/0009-net-bridge-Differentiate-MDB-additions-from-modifica.patch → patches/linux/6.18.60/0009-net-bridge-Differentiate-MDB-additions-from-modifica.patch

@@ -1,8 +1,9 @@
-From 424fd59deb93c52955dee66ebf58c3e6da005506 Mon Sep 17 00:00:00 2001
+From 7524725ed9a59da1aab4b1e25969592b407df71f Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Thu, 16 May 2024 14:51:54 +0200
-Subject: [PATCH 009/133] net: bridge: Differentiate MDB additions from
+Subject: [PATCH 009/139] net: bridge: Differentiate MDB additions from
  modifications
+Organization: Wires
 
 Before this change, the reception of an IGMPv3 report (and analogously
 for MLDv2) that adds a new group, would trigger two MDB RTM_NEWMDB

patches/linux/6.18.59/0010-nvmem-layouts-onie-tlv-Let-device-probe-even-when-TL.patch → patches/linux/6.18.60/0010-nvmem-layouts-onie-tlv-Let-device-probe-even-when-TL.patch

@@ -1,8 +1,9 @@
-From c4ff25a083b8773e089315ef60b849c1861094b7 Mon Sep 17 00:00:00 2001
+From a4d5b0da9d81cff6310d1bdb5d48b69f24c81de1 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Fri, 24 Nov 2023 23:29:55 +0100
-Subject: [PATCH 010/133] nvmem: layouts: onie-tlv: Let device probe even when
+Subject: [PATCH 010/139] nvmem: layouts: onie-tlv: Let device probe even when
  TLV is invalid
+Organization: Wires
 
 Before this change, probing an NVMEM device, expected to contain a
 valid TLV, would fail if it had not been provisioned yet. But an

patches/linux/6.18.59/0011-net-usb-r8152-add-r8153b-support-for-link-activity-L.patch → patches/linux/6.18.60/0011-net-usb-r8152-add-r8153b-support-for-link-activity-L.patch

@@ -1,8 +1,9 @@
-From c516cff652aea313ef63b7b1fdef074488833b46 Mon Sep 17 00:00:00 2001
+From 32cd1aea0bfe869e16efd4fc5f5ee093d8554d04 Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Sun, 11 Aug 2024 11:27:35 +0200
-Subject: [PATCH 011/133] net: usb: r8152: add r8153b support for link/activity
+Subject: [PATCH 011/139] net: usb: r8152: add r8153b support for link/activity
  LEDs
+Organization: Wires
 
 This patch adds support for the link/activity LEDs on the NanoPi R2S
 and OrangePi R1 Plus.

patches/linux/6.18.59/0012-arm64-dts-mediatek-mt7986a-rename-BPi-R3-ports-to-ma.patch → patches/linux/6.18.60/0012-arm64-dts-mediatek-mt7986a-rename-BPi-R3-ports-to-ma.patch

@@ -1,8 +1,9 @@
-From 1f17d0fed9deb5ee18da30170c834b5c57d0ef58 Mon Sep 17 00:00:00 2001
+From fbcfddfbdae8209f1735b7326005db3930e8885c Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Sun, 10 Aug 2025 18:52:54 +0200
-Subject: [PATCH 012/133] arm64: dts: mediatek: mt7986a: rename BPi R3 ports to
+Subject: [PATCH 012/139] arm64: dts: mediatek: mt7986a: rename BPi R3 ports to
  match case
+Organization: Wires
 
 For ref. see: https://wiki.banana-pi.org/File:Bpi-r3_Metal_case.jpg
 

patches/linux/6.18.59/0013-drm-panel-simple-Add-a-timing-for-the-Raspberry-Pi-7.patch → patches/linux/6.18.60/0013-drm-panel-simple-Add-a-timing-for-the-Raspberry-Pi-7.patch

@@ -1,8 +1,9 @@
-From b3b4640353555bb44b1bb98726dea33b17164ef4 Mon Sep 17 00:00:00 2001
+From 255876f26951f2f8cf6b1def238b1e87ebd95898 Mon Sep 17 00:00:00 2001
 From: Mattias Walström <lazzer@gmail.com>
 Date: Wed, 20 Aug 2025 21:38:24 +0200
-Subject: [PATCH 013/133] drm/panel-simple: Add a timing for the Raspberry Pi
+Subject: [PATCH 013/139] drm/panel-simple: Add a timing for the Raspberry Pi
  7" panel
+Organization: Wires
 
 The Raspberry Pi 7" 800x480 panel uses a Toshiba TC358762 DSI
 to DPI bridge chip, so there is a requirement for the timings

patches/linux/6.18.59/0014-input-touchscreen-edt-ft5x06-Add-polled-mode.patch → patches/linux/6.18.60/0014-input-touchscreen-edt-ft5x06-Add-polled-mode.patch

@@ -1,7 +1,8 @@
-From 579480ad13f26e52470d97013b28b1d6d0bd25ad Mon Sep 17 00:00:00 2001
+From 5edda772737093380cdb0037622d5357c3fac64a Mon Sep 17 00:00:00 2001
 From: Mattias Walström <lazzer@gmail.com>
 Date: Thu, 21 Aug 2025 11:20:23 +0200
-Subject: [PATCH 014/133] input:touchscreen:edt-ft5x06: Add polled mode
+Subject: [PATCH 014/139] input:touchscreen:edt-ft5x06: Add polled mode
+Organization: Wires
 
 Not all hardware has interrupts therefore we need
 to poll the touchscreen.

patches/linux/6.18.59/0015-FIX-net-dsa-mv88e6xxx-Fix-timeout-on-waiting-for-PPU.patch → patches/linux/6.18.60/0015-FIX-net-dsa-mv88e6xxx-Fix-timeout-on-waiting-for-PPU.patch

@@ -1,8 +1,9 @@
-From 3c70299a0c6ea96825d6f9235064653793e0aa81 Mon Sep 17 00:00:00 2001
+From de63c37dfc20d661c0ebcb3237a3136fc7320d09 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 12 Mar 2024 10:27:24 +0100
-Subject: [PATCH 015/133] [FIX] net: dsa: mv88e6xxx: Fix timeout on waiting for
+Subject: [PATCH 015/139] [FIX] net: dsa: mv88e6xxx: Fix timeout on waiting for
  PPU on 6393X
+Organization: Wires
 
 In a multi-chip setup, delays of up to 750ms are observed before the
 device (6393X) signals completion of PPU initialization (Global 1,

patches/linux/6.18.59/0016-net-dsa-mv88e6xxx-Improve-indirect-register-access-p.patch → patches/linux/6.18.60/0016-net-dsa-mv88e6xxx-Improve-indirect-register-access-p.patch

@@ -1,8 +1,9 @@
-From c404b9691e3d5843ca2d71a1a74143f54eaff06f Mon Sep 17 00:00:00 2001
+From cbe9b498e34cdf52e76f21840878d33ff69a54dd Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 27 Mar 2024 15:52:43 +0100
-Subject: [PATCH 016/133] net: dsa: mv88e6xxx: Improve indirect register access
+Subject: [PATCH 016/139] net: dsa: mv88e6xxx: Improve indirect register access
  perf on 6393
+Organization: Wires
 
 When operating in multi-chip mode, the 6393 family maps a subset of
 commonly used global registers to the outermost address space (in

patches/linux/6.18.59/0017-net-dsa-mv88e6xxx-Honor-ports-being-managed-via-in-b.patch → patches/linux/6.18.60/0017-net-dsa-mv88e6xxx-Honor-ports-being-managed-via-in-b.patch

@@ -1,8 +1,9 @@
-From 0e4e2f9a0a43aefe61bf2e10196cc9216997dee0 Mon Sep 17 00:00:00 2001
+From 4af390b28a48a653dfcf579f288ccef3237a97ac Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Mon, 22 Apr 2024 23:18:01 +0200
-Subject: [PATCH 017/133] net: dsa: mv88e6xxx: Honor ports being managed via
+Subject: [PATCH 017/139] net: dsa: mv88e6xxx: Honor ports being managed via
  in-band-status
+Organization: Wires
 
 Keep all link parameters in their unforced states when the port is
 declared as being managed via in-band-status, and let the MAC

patches/linux/6.18.59/0018-net-dsa-mv88e6xxx-Limit-rsvd2cpu-policy-to-user-port.patch → patches/linux/6.18.60/0018-net-dsa-mv88e6xxx-Limit-rsvd2cpu-policy-to-user-port.patch

@@ -1,8 +1,9 @@
-From 388dc8205c88f43b5add32ec6872e8ab928e6624 Mon Sep 17 00:00:00 2001
+From a79a86834fa988a3a09d35c9ea9d920fa9109cd0 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 24 Apr 2024 22:41:04 +0200
-Subject: [PATCH 018/133] net: dsa: mv88e6xxx: Limit rsvd2cpu policy to user
+Subject: [PATCH 018/139] net: dsa: mv88e6xxx: Limit rsvd2cpu policy to user
  ports on 6393X
+Organization: Wires
 
 For packets with a DA in the IEEE reserved L2 group range, originating
 from a CPU, forward it as normal, rather than classifying it as

patches/linux/6.18.59/0019-net-dsa-tag_dsa-Use-tag-priority-as-initial-skb-prio.patch → patches/linux/6.18.60/0019-net-dsa-tag_dsa-Use-tag-priority-as-initial-skb-prio.patch

@@ -1,8 +1,9 @@
-From 44e4c6768bc720d3b570d8ce0edfa82958781eb0 Mon Sep 17 00:00:00 2001
+From f4fd76e9f0635d57022844fbe390b32854153fa2 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 28 May 2024 10:38:42 +0200
-Subject: [PATCH 019/133] net: dsa: tag_dsa: Use tag priority as initial
+Subject: [PATCH 019/139] net: dsa: tag_dsa: Use tag priority as initial
  skb->priority
+Organization: Wires
 
 Use the 3-bit priority field from the DSA tag as the initial packet
 priority on ingress to the CPU.

patches/linux/6.18.59/0020-net-dsa-Support-MDB-memberships-whose-L2-addresses-o.patch → patches/linux/6.18.60/0020-net-dsa-Support-MDB-memberships-whose-L2-addresses-o.patch

@@ -1,8 +1,9 @@
-From 0275b3a1e8d4a65b7fd144f80fc1773f21712a2d Mon Sep 17 00:00:00 2001
+From cfcfbb06fa0c5c8099c0936ee70f672297b9aa34 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 16 Jan 2024 16:00:55 +0100
-Subject: [PATCH 020/133] net: dsa: Support MDB memberships whose L2 addresses
+Subject: [PATCH 020/139] net: dsa: Support MDB memberships whose L2 addresses
  overlap
+Organization: Wires
 
 Multiple IP multicast groups (32 for v4, 2^80 for v6) map to the same
 L2 address. This means that switchdev drivers may receive multiple MDB

patches/linux/6.18.59/0021-net-dsa-Support-EtherType-based-priority-overrides.patch → patches/linux/6.18.60/0021-net-dsa-Support-EtherType-based-priority-overrides.patch

@@ -1,7 +1,8 @@
-From 97dfed9ed5d4f2cf29d8541192443b184e85377a Mon Sep 17 00:00:00 2001
+From f78b51037f8912b1ffcb2b440abff3e1e0dc9acb Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Thu, 21 Mar 2024 19:12:15 +0100
-Subject: [PATCH 021/133] net: dsa: Support EtherType based priority overrides
+Subject: [PATCH 021/139] net: dsa: Support EtherType based priority overrides
+Organization: Wires
 
 ---
  include/net/dsa.h |  4 ++++

patches/linux/6.18.59/0022-net-dsa-mv88e6xxx-Support-EtherType-based-priority-o.patch → patches/linux/6.18.60/0022-net-dsa-mv88e6xxx-Support-EtherType-based-priority-o.patch

@@ -1,8 +1,9 @@
-From de8ee7a44f9b4fb42564e794d0657c974e1f797f Mon Sep 17 00:00:00 2001
+From 51333e48ba584ed1c3185ef66aacdfcc443d657f Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Fri, 22 Mar 2024 16:15:43 +0100
-Subject: [PATCH 022/133] net: dsa: mv88e6xxx: Support EtherType based priority
+Subject: [PATCH 022/139] net: dsa: mv88e6xxx: Support EtherType based priority
  overrides
+Organization: Wires
 
 ---
  drivers/net/dsa/mv88e6xxx/chip.c    | 64 +++++++++++++++++++++++++++++

patches/linux/6.18.59/0023-net-dsa-mv88e6xxx-Add-mqprio-qdisc-support.patch → patches/linux/6.18.60/0023-net-dsa-mv88e6xxx-Add-mqprio-qdisc-support.patch

@@ -1,7 +1,8 @@
-From f84774cf099db4e6cc6749398c55c971067bc0d4 Mon Sep 17 00:00:00 2001
+From 0c7366069b9ab9931b706f0683141e9a734105af Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 28 May 2024 11:04:22 +0200
-Subject: [PATCH 023/133] net: dsa: mv88e6xxx: Add mqprio qdisc support
+Subject: [PATCH 023/139] net: dsa: mv88e6xxx: Add mqprio qdisc support
+Organization: Wires
 
 Add support for attaching mqprio qdisc's to mv88e6xxx ports and use
 the packet's traffic class as the outgoing priority when no PCP bits

patches/linux/6.18.59/0024-net-dsa-mv88e6xxx-Use-VLAN-prio-over-IP-when-both-ar.patch → patches/linux/6.18.60/0024-net-dsa-mv88e6xxx-Use-VLAN-prio-over-IP-when-both-ar.patch

@@ -1,8 +1,9 @@
-From 032ea099e1fb440b6bb0469fd1be71617a695f92 Mon Sep 17 00:00:00 2001
+From 83e51ee5ae819d11a01d731dddef8e3b6a47e57c Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 29 May 2024 13:20:41 +0200
-Subject: [PATCH 024/133] net: dsa: mv88e6xxx: Use VLAN prio over IP when both
+Subject: [PATCH 024/139] net: dsa: mv88e6xxx: Use VLAN prio over IP when both
  are available
+Organization: Wires
 
 Switch the priority sourcing precdence to prefer VLAN PCP over IP
 DSCP, when both are available.

patches/linux/6.18.59/0025-FIX-net-dsa-mv88e6xxx-Trap-locally-terminated-VLANs.patch → patches/linux/6.18.60/0025-FIX-net-dsa-mv88e6xxx-Trap-locally-terminated-VLANs.patch

@@ -1,8 +1,9 @@
-From fc5944a84effc28c94796730f1ffb0d9274192bc Mon Sep 17 00:00:00 2001
+From 319396371b0dc56ea5469a140dadc402d732f9fd Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 26 Nov 2024 19:45:59 +0100
-Subject: [PATCH 025/133] [FIX] net: dsa: mv88e6xxx: Trap locally terminated
+Subject: [PATCH 025/139] [FIX] net: dsa: mv88e6xxx: Trap locally terminated
  VLANs
+Organization: Wires
 
 Before this change, in a setup like the following, packets assigned to
 VLAN 10 were forwarded between the switch ports, even though the

patches/linux/6.18.59/0026-net-dsa-mv88e6xxx-collapse-disabled-state-into-block.patch → patches/linux/6.18.60/0026-net-dsa-mv88e6xxx-collapse-disabled-state-into-block.patch

@@ -1,8 +1,9 @@
-From 9c7d43d1750b57ebb19a2f50d9ea1c300e0b0cb4 Mon Sep 17 00:00:00 2001
+From 9fb4ac02527f0ed7e121893b8ff3e8b7187fe682 Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Thu, 16 Jan 2025 12:35:12 +0100
-Subject: [PATCH 026/133] net: dsa: mv88e6xxx: collapse disabled state into
+Subject: [PATCH 026/139] net: dsa: mv88e6xxx: collapse disabled state into
  blocking
+Organization: Wires
 
 This patch changes the behavior of switchcore ports wrt. the port state.
 Instead of disabling the port, the driver now treats the disabled state