scripts/Makefile.defconf

File Facts

System

Linux kernel

Corpus path

scripts/Makefile.defconf

Extension

.defconf

Size

1063 bytes

Lines

31

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
# Configuration heplers

cmd_merge_fragments = \
	$(srctree)/scripts/kconfig/merge_config.sh \
	$4 -m -O $(objtree) $(srctree)/arch/$(SRCARCH)/configs/$2 \
	$(foreach config,$3,$(srctree)/arch/$(SRCARCH)/configs/$(config).config)

# Creates 'merged defconfigs'
# ---------------------------------------------------------------------------
# Usage:
#   $(call merge_into_defconfig,base_config,config_fragment1 config_fragment2 ...)
#
# Input config fragments without '.config' suffix
define merge_into_defconfig
	$(call cmd,merge_fragments,$1,$2)
	+$(Q)$(MAKE) -f $(srctree)/Makefile olddefconfig
endef


# Creates 'merged defconfigs without warning about overrides'
# ---------------------------------------------------------------------------
# Usage:
#   $(call merge_into_defconfig_override,base_config,config_fragment1 config_fragment2 ...)
#
# Input config fragments without '.config' suffix
define merge_into_defconfig_override
	$(call cmd,merge_fragments,$1,$2,-Q)
	+$(Q)$(MAKE) -f $(srctree)/Makefile olddefconfig
endef

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.