scripts/kconfig/tests/conditional_dep/Kconfig

Source file repositories/reference/linux-study-clean/scripts/kconfig/tests/conditional_dep/Kconfig

File Facts

System: Linux kernel
Corpus path: scripts/kconfig/tests/conditional_dep/Kconfig
Extension: [no extension]
Size: 614 bytes
Lines: 33
Domain: Support Tooling And Documentation
Bucket: scripts
Inferred role: Support Tooling And Documentation: build/configuration rule
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0
# Test Kconfig file for conditional dependencies.

# Enable module support for tristate testing
config MODULES
	bool "Enable loadable module support"
	modules
	default y

config FOO
	bool "FOO symbol"

config BAR
	bool "BAR symbol"

config TEST_BASIC
	bool "Test basic conditional dependency"
	depends on FOO if BAR
	default y

config TEST_COMPLEX
	bool "Test complex conditional dependency"
	depends on (FOO && BAR) if (FOO || BAR)
	default y

config BAZ
	tristate "BAZ symbol"

config TEST_OPTIONAL
	tristate "Test simple optional dependency"
	depends on BAZ if BAZ
	default y

Annotation

Atlas domain: Support Tooling And Documentation / scripts.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.