Searched refs:luid (Results 1 - 6 of 6) sorted by relevance

/linux-master/drivers/md/
H A Ddm-log-userspace-transfer.h15 int dm_consult_userspace(const char *uuid, uint64_t luid, int request_type,
H A Ddm-log-userspace-base.c46 uint64_t luid; member in struct:log_c
97 r = dm_consult_userspace(uuid, lc->luid, request_type, data,
108 r = dm_consult_userspace(uuid, lc->luid, DM_ULOG_CTR,
116 r = dm_consult_userspace(uuid, lc->luid, DM_ULOG_RESUME, NULL,
215 lc->luid = (unsigned long)lc;
263 r = dm_consult_userspace(lc->uuid, lc->luid, DM_ULOG_CTR,
277 r = dm_consult_userspace(lc->uuid, lc->luid, DM_ULOG_GET_REGION_SIZE,
339 (void) dm_consult_userspace(lc->uuid, lc->luid, DM_ULOG_DTR,
356 r = dm_consult_userspace(lc->uuid, lc->luid, DM_ULOG_PRESUSPEND,
373 r = dm_consult_userspace(lc->uuid, lc->luid, DM_ULOG_POSTSUSPEN
[all...]
H A Ddm-log-userspace-transfer.c154 * @luid: log's local unique identifier
170 int dm_consult_userspace(const char *uuid, uint64_t luid, int request_type, argument
203 tfr->luid = luid;
/linux-master/include/uapi/linux/
H A Ddm-log-userspace.h409 * The local unique identifier (luid) and the universally unique
412 * just the 'luid', but a cluster-aware log must use the 'uuid' and
413 * the 'luid'. The uuid is what is required for node to node
414 * communication concerning a particular log, but the 'luid' helps
418 __u64 luid; member in struct:dm_ulog_request
/linux-master/drivers/hid/
H A Dhid-sensor-custom.c756 * tag and luid is mandatory.
760 const char *luid; member in struct:hid_sensor_custom_match
782 .luid = "020B000000000000",
790 .luid = "0041010200000082",
800 .luid = "0226000171AC0081",
858 !hid_sensor_custom_prop_match_str(prop->serial_num + 5, match->luid,
948 memcpy(real_usage, match->luid, 4);
/linux-master/drivers/scsi/bfa/
H A Dbfa_defs_svc.h1023 char luid[256]; member in struct:bfa_port_fcpmap_s

Completed in 1026 milliseconds