Lines Matching refs:next
195 the CRC tag to force the next commit to fail the valid bit test if it
198 2. The valid bit alone is not enough info to know if the next commit has been
200 so it's possible that the next commit had an attempted program that left the
205 bytes in the next commit at the time it was erased.
223 | | | | +-- next commit
481 The pointer to the next metadata-pair in the directory is stored in a tail tag,
678 2. **Metadata pair (8-bytes)** - Pointer to the next metadata-pair.
683 Provides a tail pointer that points to the next metadata pair in the
686 In this case, the next metadata pair is not a part of our current directory
692 Provides a tail pointer that points to the next metadata pair in the
695 In this case, the next metadata pair belongs to the current directory. Note
696 that because directories in littlefs are sorted alphabetically, the next
795 larger to pad the commit to the next program-aligned boundary.
820 any tags in the next commit.
825 3. **Padding** - Padding to the next program-aligned boundary. No guarantees
832 bytes in the next commit at the time it was erased. This allows us to ensure