Lines Matching refs:not

25 The order of inode traversal is described as "width-first" (not to be
33 allows cramfs_lookup to return more quickly when a filename does not
56 	The block data is not compressed and should be copied verbatim.
59 	The <block_pointer> stores the actual block start offset and not
75 corresponding CRAMFS_BLK_FLAG_UNCOMPRESSED <block_ptr> bit is not set,
80 <block>s are merely byte-aligned, not generally u32-aligned.
83 <block> may be located anywhere and not necessarily contiguous with
88 is not set then the first 2 bytes of the block contains the size of the
128 This discrepancy is a bug, though it's not clear which should be
136 kernels, not even necessarily kernels of the same architecture if
181 cost is greater complexity.  Probably not worth it, but I hope someone