Re: [PATCH net-next v1] net: stmmac: Default DWMAC_MOTORCOMM to m on MACH_LOONGSON64

Next message: David Hildenbrand (Arm): "Re: [PATCH v2 1/4] mm: support promotion-only NUMA hinting scans"
Previous message: Mark Brown: "linux-next: build failure after merge of the amdgpu tree"
In reply to: Yao Zi: "Re: [PATCH net-next v1] net: stmmac: Default DWMAC_MOTORCOMM to m on MACH_LOONGSON64"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Andrew Lunn

Date: Fri Sep 18 2026 - 08:33:56 EST

> drivers/net/ethernet/marvell/octeontx2/Kconfig:54: default m
> drivers/net/ethernet/hisilicon/Kconfig:106: default m
> drivers/net/ethernet/hisilicon/Kconfig:134: default m
> drivers/net/ethernet/sun/Kconfig:77: default m
> drivers/net/ethernet/sun/Kconfig:81: default m
> drivers/net/ethernet/sun/Kconfig:89: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:37: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:47: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:67: default m
> drivers/net/ethernet/mellanox/mlxsw/Kconfig:86: default m

Look deeper at these. Apart from the sun cases, which are very old,
default m is only used for optional parts of a module, not the module
as a whole.

Andrew