Upgrade to kernel 6.18.47

configs/aarch64_defconfig

@@ -27,7 +27,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.46"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.47"
 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

@@ -27,7 +27,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.46"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.47"
 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.46"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.47"
 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.46"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.47"
 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/x86_64_defconfig

@@ -26,7 +26,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.46"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.47"
 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

@@ -26,7 +26,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.46"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.47"
 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

@@ -8,7 +8,7 @@ All notable changes to the project are documented in this file.
 
 ### Changes
 
-- Upgrade Linux kernel to 6.18.46 (LTS)
+- Upgrade Linux kernel to 6.18.47 (LTS)
 - Upgrade Buildroot to 2025.02.17 (LTS)
 - Upgrade mdns-alias to [v1.3][ma13]: fixes crash on hostname change while
   disconnected from Avahi, treats entry group failures and CNAME collisions

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

@@ -1,9 +1,8 @@
-From 7f49c30ee90aa0be9e9164a9948bfe8a1331fea6 Mon Sep 17 00:00:00 2001
+From 7d949f4f67a3135cf0b10011b938eb26d1387b71 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 19 Sep 2023 18:38:10 +0200
 Subject: [PATCH 01/64] 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.46/0002-net-phy-marvell10g-Fix-power-up-when-strapped-to-sta.patch → patches/linux/6.18.47/0002-net-phy-marvell10g-Fix-power-up-when-strapped-to-sta.patch

@@ -1,9 +1,8 @@
-From b9ab146b15ea489f948f5a11980fe924ded4daae Mon Sep 17 00:00:00 2001
+From 5eb6a022c9eb73bd78d875ff828665bf37a36466 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 21 Nov 2023 20:15:24 +0100
 Subject: [PATCH 02/64] 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.46/0003-net-phy-marvell10g-Add-LED-support-for-88X3310.patch → patches/linux/6.18.47/0003-net-phy-marvell10g-Add-LED-support-for-88X3310.patch

@@ -1,8 +1,7 @@
-From 48bf1d41a21cbe093ec241d8ee483abc70a1b8dc Mon Sep 17 00:00:00 2001
+From 3a41a84d7feffc476df7791b9454cad1702fa3e9 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 15 Nov 2023 20:58:42 +0100
 Subject: [PATCH 03/64] 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.46/0004-net-phy-marvell10g-Support-LEDs-tied-to-a-single-med.patch → patches/linux/6.18.47/0004-net-phy-marvell10g-Support-LEDs-tied-to-a-single-med.patch

@@ -1,9 +1,8 @@
-From 7f10824be067ddb40e89ccb66ebe9b0bda3a3f96 Mon Sep 17 00:00:00 2001
+From ccbfb4b449f1e7df48fce3c9dbe5d52069c0e7c6 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 12 Dec 2023 09:51:05 +0100
 Subject: [PATCH 04/64] 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.46/0005-net-phy-Do-not-resume-PHY-when-attaching.patch → patches/linux/6.18.47/0005-net-phy-Do-not-resume-PHY-when-attaching.patch

@@ -1,8 +1,7 @@
-From 60c64feacdd6a2259d09545d45227f2c44c36e53 Mon Sep 17 00:00:00 2001
+From adf5f21db3ff2efc4fe0829dad41f1fb1bd44e21 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 27 Mar 2024 10:10:19 +0100
 Subject: [PATCH 05/64] 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.46/0006-net-bridge-avoid-classifying-unknown-multicast-as-mr.patch → patches/linux/6.18.47/0006-net-bridge-avoid-classifying-unknown-multicast-as-mr.patch

@@ -1,9 +1,8 @@
-From 615860e3041a3837e09895425edd87aa16fa5965 Mon Sep 17 00:00:00 2001
+From fc97e11fd11863a45ff07cce0835fcdc53e0b01d Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Mon, 4 Mar 2024 16:47:28 +0100
 Subject: [PATCH 06/64] 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.46/0007-net-bridge-Ignore-router-ports-when-forwarding-L2-mu.patch → patches/linux/6.18.47/0007-net-bridge-Ignore-router-ports-when-forwarding-L2-mu.patch

@@ -1,9 +1,8 @@
-From bf77eac4d9bc46717a5ce5cf30bd66e17d11b16e Mon Sep 17 00:00:00 2001
+From d8df8240ba12b4d99aecb15af8d6a6be3f8bce1b Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Tue, 5 Mar 2024 06:44:41 +0100
 Subject: [PATCH 07/64] 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.46/0008-net-bridge-drop-delay-for-applying-strict-multicast-.patch → patches/linux/6.18.47/0008-net-bridge-drop-delay-for-applying-strict-multicast-.patch

@@ -1,9 +1,8 @@
-From e0fb904d3050df4c7651d04fc823a6c1dd0ef459 Mon Sep 17 00:00:00 2001
+From 0c5f2f0235bc776a861ac609987b66c9623f7e4b Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Thu, 4 Apr 2024 16:36:30 +0200
 Subject: [PATCH 08/64] 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.46/0009-net-bridge-Differentiate-MDB-additions-from-modifica.patch → patches/linux/6.18.47/0009-net-bridge-Differentiate-MDB-additions-from-modifica.patch

@@ -1,9 +1,8 @@
-From 1bc840aa52d09ab5a3f51d75674f2ac517a9ff5a Mon Sep 17 00:00:00 2001
+From cfe2b92b295081bb0304b455f367bc32a334aa4d Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Thu, 16 May 2024 14:51:54 +0200
 Subject: [PATCH 09/64] 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.46/0010-nvmem-layouts-onie-tlv-Let-device-probe-even-when-TL.patch → patches/linux/6.18.47/0010-nvmem-layouts-onie-tlv-Let-device-probe-even-when-TL.patch

@@ -1,9 +1,8 @@
-From 31ec2dddbe45228f3ad3e4f850b65125cd2b9f06 Mon Sep 17 00:00:00 2001
+From d5a2cb8bb56f01efab87dbf5d448ff63c1fc58f9 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Fri, 24 Nov 2023 23:29:55 +0100
 Subject: [PATCH 10/64] 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.46/0011-net-usb-r8152-add-r8153b-support-for-link-activity-L.patch → patches/linux/6.18.47/0011-net-usb-r8152-add-r8153b-support-for-link-activity-L.patch

@@ -1,9 +1,8 @@
-From ed17421a32311c8bdd685b65e24f83e998449305 Mon Sep 17 00:00:00 2001
+From 15f936958d2f763464c11edc62ec9b61c1f1dc29 Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Sun, 11 Aug 2024 11:27:35 +0200
 Subject: [PATCH 11/64] 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.46/0012-arm64-dts-mediatek-mt7986a-rename-BPi-R3-ports-to-ma.patch → patches/linux/6.18.47/0012-arm64-dts-mediatek-mt7986a-rename-BPi-R3-ports-to-ma.patch

@@ -1,9 +1,8 @@
-From 72267d352c38207ddb1d84af6141de93db5d150a Mon Sep 17 00:00:00 2001
+From 2795f54b4b4a49aa6e232ae0879a6d3a656bbdb1 Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Sun, 10 Aug 2025 18:52:54 +0200
 Subject: [PATCH 12/64] 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.46/0013-drm-panel-simple-Add-a-timing-for-the-Raspberry-Pi-7.patch → patches/linux/6.18.47/0013-drm-panel-simple-Add-a-timing-for-the-Raspberry-Pi-7.patch

@@ -1,9 +1,8 @@
-From 7106cd3a9e250c5e3974dd642d8cc19af5ef2ac7 Mon Sep 17 00:00:00 2001
+From bd4c9dc973ce351f1582a28042b3cdfbc229ee62 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 13/64] 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.46/0014-input-touchscreen-edt-ft5x06-Add-polled-mode.patch → patches/linux/6.18.47/0014-input-touchscreen-edt-ft5x06-Add-polled-mode.patch

@@ -1,8 +1,7 @@
-From 3bc1d86fcd0e24960152f4d758aa250057b63fcb Mon Sep 17 00:00:00 2001
+From 2607b71594b4589868ea4e7138bb68421c78c10d 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 14/64] 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.46/0015-FIX-net-dsa-mv88e6xxx-Fix-timeout-on-waiting-for-PPU.patch → patches/linux/6.18.47/0015-FIX-net-dsa-mv88e6xxx-Fix-timeout-on-waiting-for-PPU.patch

@@ -1,9 +1,8 @@
-From b0a42be0c80c3d44305f80e6e867a911aa00d35c Mon Sep 17 00:00:00 2001
+From bec7d4e077f0fe0e42c0d6d78f3ec90b606806c2 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 12 Mar 2024 10:27:24 +0100
 Subject: [PATCH 15/64] [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.46/0016-net-dsa-mv88e6xxx-Improve-indirect-register-access-p.patch → patches/linux/6.18.47/0016-net-dsa-mv88e6xxx-Improve-indirect-register-access-p.patch

@@ -1,9 +1,8 @@
-From 5810a287ae29b817a4294ebed04358f730f65065 Mon Sep 17 00:00:00 2001
+From 805ccc20298bf80c0437c8f2689e16c2711342dc Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 27 Mar 2024 15:52:43 +0100
 Subject: [PATCH 16/64] 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.46/0017-net-dsa-mv88e6xxx-Honor-ports-being-managed-via-in-b.patch → patches/linux/6.18.47/0017-net-dsa-mv88e6xxx-Honor-ports-being-managed-via-in-b.patch

@@ -1,9 +1,8 @@
-From 38a0d0b99db217d86d8b2b2b832858df24b235a0 Mon Sep 17 00:00:00 2001
+From 4ac4e05940fb8f990e1617b7f6fe2c8082f88431 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Mon, 22 Apr 2024 23:18:01 +0200
 Subject: [PATCH 17/64] 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.46/0018-net-dsa-mv88e6xxx-Limit-rsvd2cpu-policy-to-user-port.patch → patches/linux/6.18.47/0018-net-dsa-mv88e6xxx-Limit-rsvd2cpu-policy-to-user-port.patch

@@ -1,9 +1,8 @@
-From c4fffd95d964d7a911b6039cc8e7e5d736a47e4d Mon Sep 17 00:00:00 2001
+From 0e65e75f4eb35541cf5e3bf5a6b4b2a2745faefd Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 24 Apr 2024 22:41:04 +0200
 Subject: [PATCH 18/64] 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.46/0019-net-dsa-tag_dsa-Use-tag-priority-as-initial-skb-prio.patch → patches/linux/6.18.47/0019-net-dsa-tag_dsa-Use-tag-priority-as-initial-skb-prio.patch

@@ -1,9 +1,8 @@
-From 5027f6ffd52d93916153bce5bbea45e510cdde00 Mon Sep 17 00:00:00 2001
+From a9497b37fc6acf4254f8b184544513ccf8d2280b Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 28 May 2024 10:38:42 +0200
 Subject: [PATCH 19/64] 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.46/0020-net-dsa-Support-MDB-memberships-whose-L2-addresses-o.patch → patches/linux/6.18.47/0020-net-dsa-Support-MDB-memberships-whose-L2-addresses-o.patch

@@ -1,9 +1,8 @@
-From ac1320e82a14564a734664a0a8f7a0c116aaccdd Mon Sep 17 00:00:00 2001
+From 92711fe73ca534fd3d2c86c3abc70b8392b8a7d2 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 16 Jan 2024 16:00:55 +0100
 Subject: [PATCH 20/64] 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.46/0021-net-dsa-Support-EtherType-based-priority-overrides.patch → patches/linux/6.18.47/0021-net-dsa-Support-EtherType-based-priority-overrides.patch

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

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

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

patches/linux/6.18.46/0023-net-dsa-mv88e6xxx-Add-mqprio-qdisc-support.patch → patches/linux/6.18.47/0023-net-dsa-mv88e6xxx-Add-mqprio-qdisc-support.patch

@@ -1,8 +1,7 @@
-From fd4efe5794c4abc5e1d0f06f70466d6e2eccd37d Mon Sep 17 00:00:00 2001
+From 2b48492960afc3e6c39e8cdf81d9c86bfee796c4 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 28 May 2024 11:04:22 +0200
 Subject: [PATCH 23/64] 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.46/0024-net-dsa-mv88e6xxx-Use-VLAN-prio-over-IP-when-both-ar.patch → patches/linux/6.18.47/0024-net-dsa-mv88e6xxx-Use-VLAN-prio-over-IP-when-both-ar.patch

@@ -1,9 +1,8 @@
-From e9dc3d87cc9812e1b81f19ea1ad15b0492e35b91 Mon Sep 17 00:00:00 2001
+From f90ccfe9e0407d1facdf8c5f19ef569cbbe985cc Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 29 May 2024 13:20:41 +0200
 Subject: [PATCH 24/64] 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.46/0025-FIX-net-dsa-mv88e6xxx-Trap-locally-terminated-VLANs.patch → patches/linux/6.18.47/0025-FIX-net-dsa-mv88e6xxx-Trap-locally-terminated-VLANs.patch

@@ -1,9 +1,8 @@
-From 365989e8bc430a722c62fae7a54aa76d95403d44 Mon Sep 17 00:00:00 2001
+From 0259183f82fe54b2726e9c102b9672e73c558cd3 Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Tue, 26 Nov 2024 19:45:59 +0100
 Subject: [PATCH 25/64] [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.46/0026-net-dsa-mv88e6xxx-collapse-disabled-state-into-block.patch → patches/linux/6.18.47/0026-net-dsa-mv88e6xxx-collapse-disabled-state-into-block.patch

@@ -1,9 +1,8 @@
-From cc07a927ce3d66cbb5507b97d71f2e4289e3932a Mon Sep 17 00:00:00 2001
+From a62bbaed3f89a28aed57dd887120bc4255279375 Mon Sep 17 00:00:00 2001
 From: Joachim Wiberg <troglobit@gmail.com>
 Date: Thu, 16 Jan 2025 12:35:12 +0100
 Subject: [PATCH 26/64] 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

patches/linux/6.18.46/0027-net-dsa-mv88e6xxx-Only-activate-LAG-offloading-when-.patch → patches/linux/6.18.47/0027-net-dsa-mv88e6xxx-Only-activate-LAG-offloading-when-.patch

@@ -1,9 +1,8 @@
-From 293bd6b0ff1a613e7a2f864039517881f1dd7191 Mon Sep 17 00:00:00 2001
+From 53e1f993a60f9b64242a157a84f10c12df0da98c Mon Sep 17 00:00:00 2001
 From: Tobias Waldekranz <tobias@waldekranz.com>
 Date: Wed, 12 Feb 2025 22:03:14 +0100
 Subject: [PATCH 27/64] net: dsa: mv88e6xxx: Only activate LAG offloading when
  bridged
-Organization: Wires
 
 The current port isolation scheme for mv88e6xxx is detailed here:
 https://lore.kernel.org/netdev/20220203101657.990241-1-tobias@waldekranz.com/

patches/linux/6.18.46/0028-net-dsa-mv88e6xxx-Add-LED-support-for-6393X.patch → patches/linux/6.18.47/0028-net-dsa-mv88e6xxx-Add-LED-support-for-6393X.patch

@@ -1,8 +1,7 @@
-From cbdcda769e36b4c2c4870b01a02efd4223f327e1 Mon Sep 17 00:00:00 2001
+From 87e988133d1f099b4dbbb74af93a8c8ad7a7f307 Mon Sep 17 00:00:00 2001
 From: Mattias Walström <lazzer@gmail.com>
 Date: Wed, 14 Jan 2026 18:22:41 +0100
 Subject: [PATCH 28/64] net: dsa: mv88e6xxx: Add LED support for 6393X
-Organization: Wires
 
 Original commit:
 commit 462277b926140ee2d231317e92afb6cabf640268

patches/linux/6.18.46/0029-wifi-brcmfmac-support-deletion-and-recreation-of-pri.patch → patches/linux/6.18.47/0029-wifi-brcmfmac-support-deletion-and-recreation-of-pri.patch

@@ -1,12 +1,11 @@
-From 38ed86d1c1b291c40e6a15681acc09234014a271 Mon Sep 17 00:00:00 2001
+From 65c7984044af09696395ca31ca4cc4c0a0aad9cb Mon Sep 17 00:00:00 2001
 From: Mattias Walström <lazzer@gmail.com>
 Date: Thu, 15 Jan 2026 22:47:37 +0100
 Subject: [PATCH 29/64] wifi: brcmfmac: support deletion and recreation of
  primary interface
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: 8bit
-Organization: Wires
 
 The Broadcom FullMAC firmware does not allow the primary interface
 (bsscfgidx 0) to be deleted - it always exists in firmware. However,

patches/linux/6.18.46/0030-wifi-brcmfmac-check-connection-state-before-querying.patch → patches/linux/6.18.47/0030-wifi-brcmfmac-check-connection-state-before-querying.patch

@@ -1,12 +1,11 @@
-From 854fa7b14fd0e6612884a3020279f613daeaf07f Mon Sep 17 00:00:00 2001
+From b610bff927b3a626dcede03a9e310ab44c2d782d Mon Sep 17 00:00:00 2001
 From: Mattias Walström <lazzer@gmail.com>
 Date: Mon, 19 Jan 2026 13:06:53 +0100
 Subject: [PATCH 30/64] wifi: brcmfmac: check connection state before querying
  station info
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: 8bit
-Organization: Wires
 
 In station mode, brcmf_cfg80211_get_station() queries the firmware for
 station info even when not connected to an AP. This results in error