Home
last modified time | relevance | path

Searched refs:valid (Results 1 – 5 of 5) sorted by relevance

/littlefs-3.7.0-3.6.0/
DSPEC.md47 most recent metadata should be considered valid.
94 contain valid commits, only the block with the most recent revision count
190 1. Each tag contains a valid bit used to indicate if the tag and containing
191 commit is valid. After XORing, this bit should always be zero.
193 At the end of each commit, the valid bit of the previous tag is XORed
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
201 valid bit unchanged.
250 '.-----------.------------------ valid bit
260 little bit of craziness comes from the fact that the valid bit must be the
[all …]
Dlfs.c5247 bool valid = false; local
5261 if (valid && lfs_scmp(test.rev, dir->d.rev) < 0) {
5287 valid = true;
5296 if (!valid) {
/littlefs-3.7.0-3.6.0/tests/
Dtest_orphans.toml255 // is valid dir?
Dtest_relocations.toml220 // is valid dir?
Dtest_files.toml377 // with syncs we could be any size, but it at least must be valid data