tools/testing/rbtree/Makefile

File Facts

System

Linux kernel

Corpus path

tools/testing/rbtree/Makefile

Extension

[no extension]

Size

898 bytes

Lines

34

Domain

Support Tooling And Documentation

Bucket

tools

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

.PHONY: clean

TARGETS = rbtree_test interval_tree_test
OFILES = $(SHARED_OFILES) rbtree-shim.o interval_tree-shim.o maple-shim.o
DEPS = ../../../include/linux/rbtree.h \
	../../../include/linux/rbtree_types.h \
	../../../include/linux/rbtree_augmented.h \
	../../../include/linux/interval_tree.h \
	../../../include/linux/interval_tree_generic.h \
	../../../lib/rbtree.c \
	../../../lib/interval_tree.c

targets: $(TARGETS)

include ../shared/shared.mk

ifeq ($(DEBUG), 1)
	CFLAGS += -g
endif

$(TARGETS):	$(OFILES)

rbtree-shim.o: $(DEPS)
rbtree_test.o:  ../../../lib/rbtree_test.c
interval_tree-shim.o: $(DEPS)
interval_tree-shim.o: CFLAGS += -DCONFIG_INTERVAL_TREE_SPAN_ITER
interval_tree_test.o: 	../../../lib/interval_tree_test.c
interval_tree_test.o: CFLAGS += -DCONFIG_INTERVAL_TREE_SPAN_ITER

clean:
	$(RM) $(TARGETS) *.o radix-tree.c idr.c generated/*

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• 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.