Home
last modified time | relevance | path

Searched full:leads (Results 1 – 25 of 174) sorted by relevance

1234567

/linux/Documentation/timers/
H A Dhrtimers.rst19 the same way leads to a lot of compromises, macro magic and #ifdef
29 - the unpredictable [O(N)] overhead of cascading leads to delays which
31 in turn decreases robustness. Such a design still leads to rather large
/linux/drivers/media/usb/gspca/
H A Dautogain_functions.c89 80 %) and if that does not help, only then changes exposure. This leads
92 which leads to oscillating as one exposure step is huge.
/linux/kernel/trace/rv/monitors/sssw/
H A DKconfig10 Monitor to ensure sched_set_state to sleepable leads to sleeping and
/linux/arch/x86/kernel/apic/
H A DMakefile6 # Leads to non-deterministic coverage that is not a function of syscall inputs.
/linux/Documentation/core-api/
H A Dgenericirq.rst58 the flow control in the super-handler. This leads to a mix of flow logic
59 and low-level hardware logic, and it also leads to unnecessary code
87 available. This leads to a kind of duality for the time being. Over time
/linux/tools/testing/selftests/arm64/signal/
H A Dsignals.S60 * Above sigreturn should not return...looping here leads to a timeout
/linux/drivers/hid/
H A Dhid-glorious.c22 * report descriptor, which leads to inputs being ignored. Fix this
/linux/Documentation/sound/soc/
H A Doverview.rst12 CPU. This is not ideal and leads to code duplication - for example,
/linux/arch/mips/include/asm/
H A Dunroll.h13 * compiling our string functions. -funroll-all-loops leads to massive code
/linux/drivers/gpu/drm/i915/
H A Di915_file_private.h48 * VM, and then continue. This leads to a plethora of potential
H A Di915_wait_util.h53 * interrupt handler or because a spinlock_t is acquired. This leads to
/linux/include/uapi/sound/
H A Dsb16_csp.h89 * defined for some architectures like MIPS, and it leads to build errors.
/linux/arch/arc/include/asm/
H A Dsmp.h17 /* including cpumask.h leads to cyclic deps hence this Forward declaration */
/linux/tools/testing/selftests/hid/tests/
H A Dtest_usb_crash.py93 when they are actually provided a uhid device. This leads to
/linux/tools/verification/rvgen/rvgen/
H A Ddot2k.py44 buff.append("\t/* XXX: validate that this event always leads to the initial state */")
H A Dautomata.py531 # this event always leads to init
/linux/Documentation/scsi/
H A DChangeLog.megaraid40 > strange effect: reading from some files leads to the
54 > It leads to the following messages in dmesg
85 3. One member in the data structure of the driver leads to unaligned
/linux/Documentation/filesystems/fuse/
H A Dfuse-passthrough.rst73 This behavior leads to two main issues for unprivileged FUSE daemons:
/linux/tools/testing/selftests/net/af_unix/
H A Dunix_listen.c77 /* An abstract address leads with a NUL and has no filesystem entry. */ in unix_set_addr()
/linux/drivers/gpu/drm/xe/display/
H A Dxe_display_bo.c116 * leads to underflowing the bo pin count in the atomic cleanup work.
/linux/lib/
H A DKconfig.kasan193 checked. Enabling this option leads to higher memory usage.
/linux/tools/testing/selftests/bpf/progs/
H A Dcpumask_failure.c246 __failure __msg("leads to invalid memory access")
/linux/Documentation/networking/
H A Dnexthop-group-resilient.rst18 removed from the group, the ranges are recomputed, which leads to
255 Changing next-hop weights leads to change in bucket allocation::
/linux/Documentation/power/powercap/
H A Ddtpm.rst7 On the embedded world, the complexity of the SoC leads to an
/linux/drivers/net/ethernet/i825xx/
H A Dlasi_82596.c20 Examination of the mach driver leads one to believe that there

1234567