Home
last modified time | relevance | path

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

123456789

/linux/net/atm/
H A Dlec_arpc.h23 /* Push that leads to daemon */
26 /* Push that leads to daemon */
/linux/drivers/hwmon/pmbus/
H A Dbel-pfe.c22 * VOUT_MODE (0x16) is returned: it leads to incorrect exponent in linear
102 * probe which leads to probe failure (read status word failed). in pfe_pmbus_probe()
/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/arch/mips/kernel/
H A Dr4k-bugs64.c61 * The following code leads to a wrong result of the first in mult_sh_align_mod()
257 * The following code leads to a wrong result of daddiu when in check_daddiu()
/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/kernel/trace/rv/monitors/nrp/
H A Dnrp.c70 * Although need_resched leads to both the rescheduling and preempt_irq in handle_sched_need_resched()
/linux/drivers/gpu/drm/i915/
H A Di915_file_private.h48 * VM, and then continue. This leads to a plethora of potential
/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/arch/arm64/boot/dts/exynos/
H A Dexynos2200-g0s.dts106 * cpu2 and cpu3 fail to come up consistently, which leads to a hang later
/linux/tools/verification/rvgen/rvgen/
H A Ddot2k.py34 … buff.append("\t/* XXX: validate that this event always leads to the initial state */")
/linux/net/can/
H A Disotp.c7 * - RX path timeout of data reception leads to -ETIMEDOUT
8 * - RX path SN mismatch leads to -EILSEQ
9 * - RX path data reception with wrong padding leads to -EBADMSG
10 * - TX path flowcontrol reception timeout leads to -ECOMM
11 * - TX path flowcontrol reception overflow leads to -EMSGSIZE
12 * - TX path flowcontrol reception with wrong layout/padding leads to -EBADMSG
/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/drivers/spi/
H A Dspi-pxa2xx-dma.c33 * same transfer leads to problems thus we prevent concurrent calls in pxa2xx_spi_dma_transfer_complete()
/linux/Documentation/filesystems/fuse/
H A Dfuse-passthrough.rst73 This behavior leads to two main issues for unprivileged FUSE daemons:
/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/include/media/drv-intf/
H A Dsaa7146_vv.h96 (this leads to a more complicated question: shall the driver

123456789