Home
last modified time | relevance | path

Searched refs:written_count (Results 1 - 2 of 2) sorted by relevance

/third_party/f2fs-tools/fsck/
H A Dsegment.c269 u64 written_count; in f2fs_write_ex() local
301 written_count = remained_blkentries = 0; in f2fs_write_ex()
326 written_count = 0; in f2fs_write_ex()
358 written_count += len_in_blk; in f2fs_write_ex()
377 return written_count; in f2fs_write_ex()
/third_party/vulkan-loader/loader/
H A Dloader.c6588 uint32_t written_count = *pPropertyCount;
6590 icd_term->dispatch.EnumerateDeviceExtensionProperties(phys_dev_term->phys_dev, NULL, &written_count, pProperties);
6596 // After calling into the driver, written_count contains the amount of device extensions written. We can therefore write
6605 if (has_vk_extension_property_array(&cur_ext_props->props, written_count, pProperties)) {
6609 if (*pPropertyCount <= written_count) {
6613 memcpy(&pProperties[written_count], &cur_ext_props->props, sizeof(VkExtensionProperties));
6614 written_count++;
6619 *pPropertyCount = written_count;

Completed in 10 milliseconds