include/linux/mtd/partitions.h

File Facts

System

Linux kernel

Corpus path

include/linux/mtd/partitions.h

Extension

.h

Size

3946 bytes

Lines

116

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct mtd_partition
• struct mtd_info
• struct device_node
• struct mtd_part_parser_data
• struct mtd_part_parser
• struct mtd_partitions

Annotated Snippet

* once, and calling it replaces module_init() and module_exit().
 */
#define module_mtd_part_parser(__mtd_part_parser) \
	module_driver(__mtd_part_parser, register_mtd_parser, \
		      deregister_mtd_parser)

int mtd_add_partition(struct mtd_info *master, const char *name,
		      long long offset, long long length);
int mtd_del_partition(struct mtd_info *master, int partno);
uint64_t mtd_get_device_size(const struct mtd_info *mtd);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct mtd_partition`, `struct mtd_info`, `struct device_node`, `struct mtd_part_parser_data`, `struct mtd_part_parser`, `struct mtd_partitions`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: integration implementation candidate.

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.