Преглед изворни кода

Remove bogus default y for DMAR and NET_DMA

No reason I can think of of making them default y Most people don't have
the hardware and with default y they just pollute lots of configs during
make oldconfig.

Signed-off-by: Andi Kleen <ak@suse.de>
Acked-by: Jeff Garzik <jeff@garzik.org>
Acked-by: "Nelson, Shannon" <shannon.nelson@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Andi Kleen пре 17 година
родитељ
комит
4138f08d1c
2 измењених фајлова са 0 додато и 2 уклоњено
  1. 0 1
      arch/x86/Kconfig.x86_64
  2. 0 1
      drivers/dma/Kconfig

+ 0 - 1
arch/x86/Kconfig.x86_64

@@ -749,7 +749,6 @@ config PCI_DOMAINS
 config DMAR
 config DMAR
 	bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
 	bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
 	depends on PCI_MSI && ACPI && EXPERIMENTAL
 	depends on PCI_MSI && ACPI && EXPERIMENTAL
-	default y
 	help
 	help
 	  DMA remapping (DMAR) devices support enables independent address
 	  DMA remapping (DMAR) devices support enables independent address
 	  translations for Direct Memory Access (DMA) from devices.
 	  translations for Direct Memory Access (DMA) from devices.

+ 0 - 1
drivers/dma/Kconfig

@@ -43,7 +43,6 @@ comment "DMA Clients"
 config NET_DMA
 config NET_DMA
 	bool "Network: TCP receive copy offload"
 	bool "Network: TCP receive copy offload"
 	depends on DMA_ENGINE && NET
 	depends on DMA_ENGINE && NET
-	default y
 	help
 	help
 	  This enables the use of DMA engines in the network stack to
 	  This enables the use of DMA engines in the network stack to
 	  offload receive copy-to-user operations, freeing CPU cycles.
 	  offload receive copy-to-user operations, freeing CPU cycles.