| /linux-6.1.9/drivers/usb/class/ |
| D | cdc-wdm.c | 84 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.1.9/crypto/asymmetric_keys/ |
| D | x509.asn1 | 12 validity Validity,
|
| /linux-6.1.9/tools/testing/selftests/powerpc/math/ |
| D | vsx_asm.S | 27 # validity of the VMX registers while running is not zero.
|
| D | fpu_asm.S | 98 # has been loaded with darray. Will proceed to check the validity of the FPU
|
| D | vmx_asm.S | 114 # the VMX have been loaded with varray. Will proceed to check the validity of
|
| /linux-6.1.9/Documentation/virt/kvm/s390/ |
| D | s390-pv.rst | 41 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.1.9/arch/s390/include/asm/ |
| D | cio.h | 279 u32 validity:3; member
|
| /linux-6.1.9/net/ceph/ |
| D | auth_x.c | 171 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.1.9/Documentation/admin-guide/device-mapper/ |
| D | dm-init.rst | 42 the validity of associated metadata.
|
| D | dm-zoned.rst | 77 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.1.9/drivers/s390/block/ |
| D | dasd_eckd.c | 565 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()
584 pfxdata->validity.time_stamp = 1; /* 'Time Stamp Valid' */ 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()
4376 pfxdata.validity.time_stamp = 1; /* 'Time Stamp Valid' */ in prepare_itcw()
[all …]
|
| D | dasd_eckd.h | 242 } __attribute__ ((packed)) validity; member
|
| /linux-6.1.9/sound/pci/mixart/ |
| D | mixart_core.h | 250 u32 validity; member
|
| /linux-6.1.9/Documentation/networking/ |
| D | dccp.rst | 176 the local ackno validity and the remote seqno validity windows (7.5.1).
|
| /linux-6.1.9/Documentation/userspace-api/media/v4l/ |
| D | vidioc-create-bufs.rst | 89 created buffers, and it will check the validity of ``memory`` and
|
| /linux-6.1.9/Documentation/driver-api/media/drivers/ |
| D | radiotrack.rst | 18 validity of this information. No other documentation on the AIMS
|
| /linux-6.1.9/arch/alpha/lib/ |
| D | stxcpy.S | 281 and t1, t2, t1 # e1 : to source validity mask
|
| D | ev6-stxcpy.S | 311 and t1, t2, t1 # E : to source validity mask
|
| D | stxncpy.S | 339 zapnot t1, t8, t1 # .. e1 : to source validity mask
|
| D | ev6-stxncpy.S | 388 zapnot t1, t8, t1 # U : to source validity mask
|
| /linux-6.1.9/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 88 In those cases, however, the above validity considerations must be taken into
|
| /linux-6.1.9/Documentation/devicetree/bindings/arm/ |
| D | cpu-capacity.txt | 26 no guarantees on the validity or suitability of any particular benchmark, the
|
| /linux-6.1.9/lib/ |
| D | Kconfig.kasan | 174 Makes KASAN check the validity of accesses to vmalloc allocations.
|
| /linux-6.1.9/Documentation/virt/coco/ |
| D | sev-guest.rst | 126 command. It provides the following assurances regarding the validity of CPUID
|
| /linux-6.1.9/Documentation/dev-tools/ |
| D | kasan.rst | 50 Software KASAN modes use compile-time instrumentation to insert validity checks
299 access validity. It is currently only implemented for the arm64 architecture.
426 Software KASAN modes use compiler instrumentation to insert validity checks.
|