tools/include/nolibc/sys/sysmacros.h
Source file repositories/reference/linux-study-clean/tools/include/nolibc/sys/sysmacros.h
File Facts
- System
- Linux kernel
- Corpus path
tools/include/nolibc/sys/sysmacros.h- Extension
.h- Size
- 892 bytes
- Lines
- 38
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
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
../nolibc.h../std.h
Detected Declarations
function Copyrightfunction __nolibc_majorfunction __nolibc_minor
Annotated Snippet
#include "../nolibc.h"
#ifndef _NOLIBC_SYS_SYSMACROS_H
#define _NOLIBC_SYS_SYSMACROS_H
#include "../std.h"
static __inline__ dev_t __nolibc_makedev(unsigned int maj, unsigned int min)
{
return (((dev_t)maj & ~0xfff) << 32) | ((maj & 0xfff) << 8) |
(((dev_t)min & ~0xff) << 12) | (min & 0xff);
}
#define makedev(maj, min) __nolibc_makedev(maj, min)
static __inline__ unsigned int __nolibc_major(dev_t dev)
{
return ((dev >> 32) & ~0xfff) | ((dev >> 8) & 0xfff);
}
#define major(dev) __nolibc_major(dev)
static __inline__ unsigned int __nolibc_minor(dev_t dev)
{
return ((dev >> 12) & ~0xff) | (dev & 0xff);
}
#define minor(dev) __nolibc_minor(dev)
#endif /* _NOLIBC_SYS_SYSMACROS_H */
Annotation
- Immediate include surface: `../nolibc.h`, `../std.h`.
- Detected declarations: `function Copyright`, `function __nolibc_major`, `function __nolibc_minor`.
- Atlas domain: Support Tooling And Documentation / tools.
- 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.