Home
last modified time | relevance | path

Searched refs:validity (Results 1 – 25 of 62) sorted by relevance

123

/Linux-v5.4/fs/cachefiles/
Dxattr.c161 enum fscache_checkaux validity; in cachefiles_check_auxdata() local
182 validity = fscache_check_aux(&object->fscache, &auxbuf->data, xlen, in cachefiles_check_auxdata()
184 if (validity != FSCACHE_CHECKAUX_OKAY) in cachefiles_check_auxdata()
/Linux-v5.4/drivers/usb/class/
Dcdc-wdm.c78 struct urb *validity; member
325 usb_kill_urb(desc->validity); in kill_urbs()
331 usb_free_urb(desc->validity); in free_urbs()
664 rv = usb_submit_urb(desc->validity, GFP_KERNEL); in wdm_open()
824 desc->validity = usb_alloc_urb(0, GFP_KERNEL); in wdm_create()
825 if (!desc->validity) in wdm_create()
849 desc->validity, in wdm_create()
1052 rv = usb_submit_urb(desc->validity, GFP_NOIO); in recover_from_urb_loss()
/Linux-v5.4/crypto/asymmetric_keys/
Dx509.asn112 validity Validity,
/Linux-v5.4/tools/testing/selftests/powerpc/math/
Dvsx_asm.S27 # validity of the VMX registers while running is not zero.
Dfpu_asm.S98 # has been loaded with darray. Will proceed to check the validity of the FPU
Dvmx_asm.S114 # the VMX have been loaded with varray. Will proceed to check the validity of
/Linux-v5.4/net/ceph/
Dauth_x.c168 struct timespec64 validity; in process_one_ticket() local
208 ceph_decode_timespec64(&validity, dp); in process_one_ticket()
210 new_expires = ktime_get_real_seconds() + validity.tv_sec; in process_one_ticket()
211 new_renew_after = new_expires - (validity.tv_sec / 4); in process_one_ticket()
/Linux-v5.4/arch/s390/include/asm/
Dcio.h279 u32 validity:3; member
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Ddm-zoned.rst73 3) A set of blocks used to store bitmaps indicating the validity of
94 Read operations are processed according to the block validity
Ddm-init.rst42 the validity of associated metadata.
/Linux-v5.4/Documentation/networking/
Ddccp.txt169 the local ackno validity and the remote seqno validity windows (7.5.1).
/Linux-v5.4/sound/pci/mixart/
Dmixart_core.h249 u32 validity; member
/Linux-v5.4/Documentation/devicetree/bindings/net/dsa/
Dsja1105.txt16 are required in order to be able to statically check their validity.
/Linux-v5.4/drivers/s390/block/
Ddasd_eckd.c525 pfxdata->validity.define_extent = 1; in prefix_LRE()
529 pfxdata->validity.verify_base = 1; in prefix_LRE()
532 pfxdata->validity.verify_base = 1; in prefix_LRE()
533 pfxdata->validity.hyper_pav = 1; in prefix_LRE()
544 pfxdata->validity.time_stamp = 1; /* 'Time Stamp Valid' */ in prefix_LRE()
4094 pfxdata.validity.define_extent = 1; in prepare_itcw()
4098 pfxdata.validity.verify_base = 1; in prepare_itcw()
4101 pfxdata.validity.verify_base = 1; in prepare_itcw()
4102 pfxdata.validity.hyper_pav = 1; in prepare_itcw()
4132 pfxdata.validity.time_stamp = 1; /* 'Time Stamp Valid' */ in prepare_itcw()
[all …]
Ddasd_eckd.h235 } __attribute__ ((packed)) validity; member
/Linux-v5.4/arch/alpha/lib/
Dstxcpy.S281 and t1, t2, t1 # e1 : to source validity mask
Dev6-stxcpy.S311 and t1, t2, t1 # E : to source validity mask
Dstxncpy.S339 zapnot t1, t8, t1 # .. e1 : to source validity mask
Dev6-stxncpy.S388 zapnot t1, t8, t1 # U : to source validity mask
/Linux-v5.4/Documentation/media/uapi/v4l/
Dvidioc-create-bufs.rst98 created buffers, and it will check the validity of ``memory`` and
/Linux-v5.4/Documentation/devicetree/bindings/arm/
Dcpu-capacity.txt26 no guarantees on the validity or suitability of any particular benchmark, the
/Linux-v5.4/Documentation/media/v4l-drivers/
Dradiotrack.rst18 validity of this information. No other documentation on the AIMS
/Linux-v5.4/Documentation/firmware-guide/acpi/
DDSD-properties-rules.rst84 In those cases, however, the above validity considerations must be taken into
/Linux-v5.4/Documentation/dev-tools/
Dkasan.rst12 KASAN uses compile-time instrumentation to insert validity checks before every
/Linux-v5.4/Documentation/i2c/
Ddev-interface.rst202 come from user-space for validity. After this point, there is no

123