net/mctp/Kconfig

Source file repositories/reference/linux-study-clean/net/mctp/Kconfig

File Facts

System: Linux kernel
Corpus path: net/mctp/Kconfig
Extension: [no extension]
Size: 706 bytes
Lines: 25
Domain: Networking Core
Bucket: Sockets, Protocols, Packet Path, And Network Policy
Inferred role: Networking Core: build/configuration rule
Status: atlas-only

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

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

menuconfig MCTP
	depends on NET
	bool "MCTP core protocol support"
	help
	  Management Component Transport Protocol (MCTP) is an in-system
	  protocol for communicating between management controllers and
	  their managed devices (peripherals, host processors, etc.). The
	  protocol is defined by DMTF specification DSP0236.

	  This option enables core MCTP support. For communicating with other
	  devices, you'll want to enable a driver for a specific hardware
	  channel.

config MCTP_TEST
        bool "MCTP core tests" if !KUNIT_ALL_TESTS
        select MCTP_FLOWS
        depends on MCTP=y && KUNIT=y
        default KUNIT_ALL_TESTS

config MCTP_FLOWS
	bool
	depends on MCTP
	select SKB_EXTENSIONS

Annotation

Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
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.