Home
last modified time | relevance | path

Searched full:completely (Results 1 – 25 of 1422) sorted by relevance

12345678910>>...57

/linux-6.14.4/Documentation/userspace-api/media/v4l/
Dselection-api-configuration.rst39 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/
Dopal-kmsg.c19 * 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/
Dtrace_clock.c50 * 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/
Dmlxsw.rst99 completely
105 completely
/linux-6.14.4/Documentation/driver-api/nvdimm/
Dfirmware-activate.rst46 '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/
Dnzxt-smart2.rst21 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/
Dpio.h71 * but not completely written to the chip, yet.
74 /* Packets on the txrunning queue are completely
/linux-6.14.4/Documentation/fb/
Ds3fb.rst12 S3 Plato/PX (completely untested)
13 S3 Aurora64V+ (completely untested)
/linux-6.14.4/fs/xfs/
DKconfig10 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/
Dmasklog.h21 * 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/
Dbr_private_mrp.h52 * backup in case the HW can't implement completely the protocol.
57 * BR_MRP_HW - the HW can implement completely the protocol.
Dbr_mrp_switchdev.c86 /* 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/
Dosi.rst57 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/
Drpc-server-gss.rst24 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/
Dsystem-state.rst9 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/
Dxfarray.h136 /* 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/
Dtnum.h22 /* A completely unknown value */
70 /* Returns true if @a is completely unknown */
/linux-6.14.4/Documentation/driver-api/driver-model/
Ddriver.rst29 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/
Dringbuf.rst106 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/
Ddma.h8 * MAX_DMA_ADDRESS is ambiguous because on s390 its completely unrelated
/linux-6.14.4/arch/um/include/asm/
Dcache.h11 /* XXX: this was taken from x86, now it's completely random. Luckily only
/linux-6.14.4/Documentation/arch/arm/
Dmicrochip.rst13 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/
Dbrcm,bcm7120-l2-intc.yaml117 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/
Dminimal.bpf.c3 * A completely minimal scheduler.
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-platform-devices-occ-hwmon8 completely read by a user. As the name suggests, only the data

12345678910>>...57