netdev - Re: [PATCH net-next] net: lantiq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <395bfe98-146c-4da3-9c2f-362f548da59f@intel.com>
Date: Thu, 29 Jan 2026 14:56:10 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Heiner Kallweit <hkallweit1@...il.com>, Jakub Kicinski <kuba@...nel.org>,
	Paolo Abeni <pabeni@...hat.com>, David Miller <davem@...emloft.net>, "Eric
 Dumazet" <edumazet@...gle.com>, Simon Horman <horms@...nel.org>, Andrew Lunn
	<andrew+netdev@...n.ch>, Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
	Vadim Fedorenko <vadim.fedorenko@...ux.dev>, Lorenzo Bianconi
	<lorenzo@...nel.org>, Hauke Mehrtens <hauke@...ke-m.de>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>, "OpenWrt
 Development List" <openwrt-devel@...ts.openwrt.org>, Daniel Golle
	<daniel@...rotopia.org>
Subject: Re: [PATCH net-next] net: lantiq_etop: remove driver



On 1/29/2026 9:18 AM, Heiner Kallweit wrote:
> This driver in mainline lost its in-tree user with commit cd93b4895ea5
> ("MIPS: lantiq: drop mips_machine support") in 2012. Since then it has
> had no in-tree user. Only user seems to be OpenWRT, with several changes
> to the in-tree driver version:
> target/linux/lantiq/patches-6.12/035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch
> target/linux/lantiq/patches-6.12/028-NET-lantiq-various-etop-fixes.patch
> target/linux/lantiq/patches-6.12/701-NET-lantiq-etop-of-mido.patch
> So it seems the driver is maintained in OpenWrt only, except tree-wide
> in-tree changes. According to OpenWRT maintainers it would be ok to
> remove the driver in mainline and keep it downstream only (see linked
> conversation).
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@...il.com>
> Link: https://lore.kernel.org/netdev/d80fef86-ba14-4bd4-bce5-4d61a75d591b@hauke-m.de/T/#t
> --- 
Makes sense.

Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>