Home
last modified time | relevance | path

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

123

/linux-6.3-rc2/drivers/usb/class/
A Dcdc-wdm.c84 struct urb *validity; member
342 usb_poison_urb(desc->validity); in poison_urbs()
353 usb_unpoison_urb(desc->validity); in unpoison_urbs()
359 usb_free_urb(desc->validity); in free_urbs()
741 rv = usb_submit_urb(desc->validity, GFP_KERNEL); in wdm_open()
851 return usb_submit_urb(desc->validity, GFP_KERNEL); in wdm_wwan_port_start()
1053 desc->validity = usb_alloc_urb(0, GFP_KERNEL); in wdm_create()
1054 if (!desc->validity) in wdm_create()
1078 desc->validity, in wdm_create()
1289 rv = usb_submit_urb(desc->validity, GFP_NOIO); in recover_from_urb_loss()
/linux-6.3-rc2/crypto/asymmetric_keys/
A Dx509.asn112 validity Validity,
/linux-6.3-rc2/tools/testing/selftests/powerpc/math/
A Dvsx_asm.S27 # validity of the VMX registers while running is not zero.
A Dfpu_asm.S98 # has been loaded with darray. Will proceed to check the validity of the FPU
A Dvmx_asm.S114 # the VMX have been loaded with varray. Will proceed to check the validity of
/linux-6.3-rc2/Documentation/virt/kvm/s390/
A Ds390-pv.rst41 at the time of injection, a validity interception is recognized. The
93 discussed before. Other data is either ignored or results in validity
/linux-6.3-rc2/arch/s390/include/asm/
A Dcio.h279 u32 validity:3; member
/linux-6.3-rc2/net/ceph/
A Dauth_x.c171 struct timespec64 validity; in process_one_ticket() local
212 ceph_decode_timespec64(&validity, dp); in process_one_ticket()
214 new_expires = ktime_get_real_seconds() + validity.tv_sec; in process_one_ticket()
215 new_renew_after = new_expires - (validity.tv_sec / 4); in process_one_ticket()
/linux-6.3-rc2/Documentation/admin-guide/device-mapper/
A Ddm-init.rst42 the validity of associated metadata.
A Ddm-zoned.rst77 3) A set of blocks used to store bitmaps indicating the validity of
98 Read operations are processed according to the block validity
/linux-6.3-rc2/drivers/s390/block/
A Ddasd_eckd.c565 pfxdata->validity.define_extent = 1; in prefix_LRE()
569 pfxdata->validity.verify_base = 1; in prefix_LRE()
572 pfxdata->validity.verify_base = 1; in prefix_LRE()
573 pfxdata->validity.hyper_pav = 1; in prefix_LRE()
4338 pfxdata.validity.define_extent = 1; in prepare_itcw()
4342 pfxdata.validity.verify_base = 1; in prepare_itcw()
4345 pfxdata.validity.verify_base = 1; in prepare_itcw()
4346 pfxdata.validity.hyper_pav = 1; in prepare_itcw()
4937 pfxdata->validity.verify_base = 0; in dasd_eckd_reset_ccw_to_base_io()
4938 pfxdata->validity.hyper_pav = 0; in dasd_eckd_reset_ccw_to_base_io()
[all …]
A Ddasd_eckd.h242 } __attribute__ ((packed)) validity; member
/linux-6.3-rc2/sound/pci/mixart/
A Dmixart_core.h250 u32 validity; member
/linux-6.3-rc2/Documentation/networking/
A Ddccp.rst176 the local ackno validity and the remote seqno validity windows (7.5.1).
/linux-6.3-rc2/Documentation/userspace-api/media/v4l/
A Dvidioc-create-bufs.rst89 created buffers, and it will check the validity of ``memory`` and
/linux-6.3-rc2/Documentation/devicetree/bindings/cpu/
A Dcpu-capacity.txt26 no guarantees on the validity or suitability of any particular benchmark, the
/linux-6.3-rc2/Documentation/driver-api/media/drivers/
A Dradiotrack.rst18 validity of this information. No other documentation on the AIMS
/linux-6.3-rc2/arch/alpha/lib/
A Dstxcpy.S281 and t1, t2, t1 # e1 : to source validity mask
A Dev6-stxcpy.S311 and t1, t2, t1 # E : to source validity mask
A Dstxncpy.S339 zapnot t1, t8, t1 # .. e1 : to source validity mask
A Dev6-stxncpy.S388 zapnot t1, t8, t1 # U : to source validity mask
/linux-6.3-rc2/Documentation/firmware-guide/acpi/
A DDSD-properties-rules.rst88 In those cases, however, the above validity considerations must be taken into
/linux-6.3-rc2/lib/
A DKconfig.kasan183 Makes KASAN check the validity of accesses to vmalloc allocations.
/linux-6.3-rc2/Documentation/virt/coco/
A Dsev-guest.rst126 command. It provides the following assurances regarding the validity of CPUID
/linux-6.3-rc2/Documentation/dev-tools/
A Dkasan.rst50 Software KASAN modes use compile-time instrumentation to insert validity checks
316 access validity. It is currently only implemented for the arm64 architecture.
443 Software KASAN modes use compiler instrumentation to insert validity checks.

Completed in 58 milliseconds

123