scripts/kconfig/tests/err_transitional/Kconfig
Source file repositories/reference/linux-study-clean/scripts/kconfig/tests/err_transitional/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
scripts/kconfig/tests/err_transitional/Kconfig- Extension
[no extension]- Size
- 936 bytes
- Lines
- 53
- 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 that transitional symbols cannot have properties other than help
config BAD_DEFAULT
bool
transitional
default y
help
This transitional symbol illegally has a default property.
config BAD_PROMPT
bool
transitional
prompt "Bad prompt"
help
This transitional symbol illegally has a prompt.
config BAD_SELECT
bool
transitional
select OTHER_SYMBOL
help
This transitional symbol illegally has a select.
config BAD_IMPLY
bool
transitional
imply OTHER_SYMBOL
help
This transitional symbol illegally has an imply.
config BAD_DEPENDS
bool
transitional
depends on OTHER_SYMBOL
help
This transitional symbol illegally has a depends.
config BAD_RANGE
int
transitional
range 1 10
help
This transitional symbol illegally has a range.
config BAD_NO_TYPE
transitional
help
This transitional symbol illegally has no type specified.
config OTHER_SYMBOL
bool
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.