tools/testing/selftests/drivers/net/dsa/Makefile

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/drivers/net/dsa/Makefile

Extension

[no extension]

Size

966 bytes

Lines

37

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+ OR MIT

TEST_PROGS := \
	bridge_locked_port.sh \
	bridge_mdb.sh \
	bridge_mld.sh \
	bridge_vlan_aware.sh \
	bridge_vlan_mcast.sh \
	bridge_vlan_unaware.sh \
	local_termination.sh \
	no_forwarding.sh \
	tc_actions.sh \
	test_bridge_fdb_stress.sh \
# end of TEST_PROGS

TEST_FILES := \
	forwarding.config \
	run_net_forwarding_test.sh \
# end of TEST_FILES

TEST_INCLUDES := \
	../../../net/forwarding/bridge_locked_port.sh \
	../../../net/forwarding/bridge_mdb.sh \
	../../../net/forwarding/bridge_mld.sh \
	../../../net/forwarding/bridge_vlan_aware.sh \
	../../../net/forwarding/bridge_vlan_mcast.sh \
	../../../net/forwarding/bridge_vlan_unaware.sh \
	../../../net/forwarding/lib.sh \
	../../../net/forwarding/local_termination.sh \
	../../../net/forwarding/no_forwarding.sh \
	../../../net/forwarding/tc_actions.sh \
	../../../net/forwarding/tc_common.sh \
	../../../net/lib.sh \
# end of TEST_INCLUDES

include ../../../lib.mk

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.