Searched full:user (Results 1 – 6 of 6) sorted by relevance
100 usage for performance, and optional static buffers if the user wants to avoid104 to the user to allocate, allowing multiple filesystems to be in use105 simultaneously. With the `lfs_t` and configuration struct, a user can110 structures must be provided by the user.123 [lfs.h](lfs.h), or an error returned by the user's block device operations.126 user may return a `LFS_ERR_CORRUPT` error if the implementation already can
542 Attaches a user attribute to an id.544 littlefs has a concept of "user attributes". These are small user-provided548 Each user attribute is uniquely identified by an 8-bit type which is stored in549 the chunk field, and the user attribute itself can be found in the tag's data.551 There are currently no standard user attributes and a portable littlefs552 implementation should work with any user attributes missing.554 Layout of the user-attr tag:567 User-attr fields:569 1. **Attr type (8-bits)** - Type of the user attributes.571 2. **Attr data** - The data associated with the user attribute.
152 // Opaque user provided context that can be used to pass157 // to the user.162 // been erased. Negative error codes are propogated to the user.169 // are propogated to the user.174 // are propogated to the user.263 // 8-bit type of attribute, provided by user and used to
124 qemu-user153 qemu-user182 qemu-user331 git config user.name "geky bot"332 git config user.email "bot@geky.net"
9 // Only compile if user does not provide custom config
1836 it isn't user facing and we can handle the corner cases internally.1844 file as moving in order to make the move atomic from the user perspective.
