drivers/md/dm-vdo/string-utils.h

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-vdo/string-utils.h

Extension

.h

Size

514 bytes

Lines

24

Domain

Driver Families

Bucket

drivers/md

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

• linux/kernel.h
• linux/string.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef VDO_STRING_UTILS_H
#define VDO_STRING_UTILS_H

#include <linux/kernel.h>
#include <linux/string.h>

/* Utilities related to string manipulation */

static inline const char *vdo_bool_to_string(bool value)
{
	return value ? "true" : "false";
}

/* Append a formatted string to the end of a buffer. */
char *vdo_append_to_buffer(char *buffer, char *buf_end, const char *fmt, ...)
	__printf(3, 4);

#endif /* VDO_STRING_UTILS_H */

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/string.h`.
• Atlas domain: Driver Families / drivers/md.
• Implementation status: source 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.