Skip to contentSkip to conversation

MIPS: ath79: remove obsolete ATH79_DEV_* configs

PATCH Applied Lukas Bulwahn 2 participants 2 messages Mar 16, 2023 – Mar 17, 2023

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MIPS: ath79: remove obsolete ATH79_DEV_* configs

Commit 85b9686dae30 ("MIPS: ath79: drop platform device registration code") removes all files arch/mips/ath79/dev-*.[ch], adjusts the Makefile, but misses to adjust the Kconfig file. Hence, since then, the configs ATH79_DEV_* are really dead.

Commit 3a77e0d75eed ("MIPS: ath79: drop machfiles") already removes all configs that select ATH79_DEV_* config. So at that point, they was not a way to enable them with a kernel build configuration.

Remove these obsolete ATH79_DEV_* configs.

---
 arch/mips/ath79/Kconfig | 16 ----------------
 1 file changed, 16 deletions(-)
arch/mips/ath79/Kconfig +0 -16
index 7367416642cb..04154128c4de 100644
@@ -29,20 +29,4 @@ config SOC_QCA955X
 config PCI_AR724X
 	def_bool n
 
-config ATH79_DEV_GPIO_BUTTONS
-	def_bool n
-
-config ATH79_DEV_LEDS_GPIO
-	def_bool n
-
-config ATH79_DEV_SPI
-	def_bool n
-
-config ATH79_DEV_USB
-	def_bool n
-
-config ATH79_DEV_WMAC
-	depends on (SOC_AR913X || SOC_AR933X || SOC_AR934X || SOC_QCA955X)
-	def_bool n
-
 endif
Signature · 1 line
2.17.1
maintainer Applied
#1 lore raw
Quoted 9 lines · Lukas Bulwahn

Commit 85b9686dae30 ("MIPS: ath79: drop platform device registration code") removes all files arch/mips/ath79/dev-*.[ch], adjusts the Makefile, but misses to adjust the Kconfig file. Hence, since then, the configs ATH79_DEV_* are really dead.

Commit 3a77e0d75eed ("MIPS: ath79: drop machfiles") already removes all configs that select ATH79_DEV_* config. So at that point, they was not a way to enable them with a kernel build configuration.

Quoted 6 lines

Remove these obsolete ATH79_DEV_* configs.

---
 arch/mips/ath79/Kconfig | 16 ----------------
 1 file changed, 16 deletions(-)

applied to mips-next.

Thomas.

Signature · 2 lines
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]