Searched full:completely (Results 1 – 25 of 1422) sorted by relevance
12345678910>>...57
/linux-6.14.4/Documentation/userspace-api/media/v4l/ |
D | selection-api-configuration.rst | 39 active cropping area must lie completely inside the capture boundaries. 58 bounds rectangle. The composing rectangle must lie completely inside 99 must lie completely inside the crop boundaries and the driver may 110 composing rectangle must lie completely inside the bounds rectangle. The
|
/linux-6.14.4/arch/powerpc/platforms/powernv/ |
D | opal-kmsg.c | 19 * may not be completely printed. This function does not actually dump the 20 * message, it just ensures that OPAL completely flushes the console buffer.
|
/linux-6.14.4/kernel/trace/ |
D | trace_clock.c | 50 * trace_clock(): 'between' trace clock. Not completely serialized, 51 * but not completely incorrect when crossing CPUs either. 65 * Note that this use of jiffies_64 is not completely safe on
|
/linux-6.14.4/Documentation/networking/devlink/ |
D | mlxsw.rst | 99 completely 105 completely
|
/linux-6.14.4/Documentation/driver-api/nvdimm/ |
D | firmware-activate.rst | 46 'ndbusX/firmware/activate' property will be elided completely if no 57 elided completely if no firmware activation capability is detected.
|
/linux-6.14.4/Documentation/hwmon/ |
D | nzxt-smart2.rst | 21 Also, the device has a noise sensor, but the sensor seems to be completely 53 attribute to 0 turns off the fan completely.
|
/linux-6.14.4/drivers/net/wireless/broadcom/b43legacy/ |
D | pio.h | 71 * but not completely written to the chip, yet. 74 /* Packets on the txrunning queue are completely
|
/linux-6.14.4/Documentation/fb/ |
D | s3fb.rst | 12 S3 Plato/PX (completely untested) 13 S3 Aurora64V+ (completely untested)
|
/linux-6.14.4/fs/xfs/ |
D | Kconfig | 10 on the SGI IRIX platform. It is completely multi-threaded, can 93 they are completely independent subsystems. 114 mechanism for ensuring data and metadata/log I/Os are completely
|
/linux-6.14.4/fs/ocfs2/cluster/ |
D | masklog.h | 21 * long tests, though, completely avoiding tests that can never pass if the 99 * than errors and notices, allowing gcc to remove the code completely. 155 * call completely when (m & ML_ALLOWED_BITS) is 0.
|
/linux-6.14.4/net/bridge/ |
D | br_private_mrp.h | 52 * backup in case the HW can't implement completely the protocol. 57 * BR_MRP_HW - the HW can implement completely the protocol.
|
D | br_mrp_switchdev.c | 86 /* If the driver can't configure to run completely the protocol in HW, in br_mrp_switchdev_set_ring_role() 164 /* If the driver can't configure to run completely the protocol in HW, in br_mrp_switchdev_set_in_role()
|
/linux-6.14.4/Documentation/firmware-guide/acpi/ |
D | osi.rst | 57 completely unrelated code on completely unrelated systems. This prompted 124 This strategy is problematic, as Linux is never completely compatible with
|
/linux-6.14.4/Documentation/filesystems/nfs/ |
D | rpc-server-gss.rst | 24 Authentication for NFS. Although GSSAPI is itself completely mechanism 31 GSSAPI is a complex library, and implementing it completely in kernel is
|
/linux-6.14.4/Documentation/livepatch/ |
D | system-state.rst | 9 Each new livepatch completely replaces any older one. It can keep, 71 - Any completely new system state modification is allowed.
|
/linux-6.14.4/fs/xfs/scrub/ |
D | xfarray.h | 136 /* First array index in folio that is completely readable */ 139 /* Last array index in folio that is completely readable */
|
/linux-6.14.4/include/linux/ |
D | tnum.h | 22 /* A completely unknown value */ 70 /* Returns true if @a is completely unknown */
|
/linux-6.14.4/Documentation/driver-api/driver-model/ |
D | driver.rst | 29 being converted completely to the new model:: 41 Most drivers will not be able to be converted completely to the new 48 completely bus-specific. Defining them as bus-specific entities would
|
/linux-6.14.4/Documentation/bpf/ |
D | ringbuf.rst | 106 completely. But in exchange, it only allows a known constant size of memory to 180 completely lockless and independent. All records become available to consumer 191 appear completely contiguous in virtual memory. See comment and a simple ASCII
|
/linux-6.14.4/arch/s390/include/asm/ |
D | dma.h | 8 * MAX_DMA_ADDRESS is ambiguous because on s390 its completely unrelated
|
/linux-6.14.4/arch/um/include/asm/ |
D | cache.h | 11 /* XXX: this was taken from x86, now it's completely random. Luckily only
|
/linux-6.14.4/Documentation/arch/arm/ |
D | microchip.rst | 13 development process even if this product prefix has completely disappeared from 212 considered as "Unstable". To be completely clear, any at91 binding can change at
|
/linux-6.14.4/Documentation/devicetree/bindings/interrupt-controller/ |
D | brcm,bcm7120-l2-intc.yaml | 117 outputs bypass this 2nd level interrupt controller completely; it is 118 completely transparent for the interrupt controller parent. This should
|
/linux-6.14.4/tools/testing/selftests/sched_ext/ |
D | minimal.bpf.c | 3 * A completely minimal scheduler.
|
/linux-6.14.4/Documentation/ABI/testing/ |
D | sysfs-bus-platform-devices-occ-hwmon | 8 completely read by a user. As the name suggests, only the data
|
12345678910>>...57