Home
last modified time | relevance | path

Searched full:lead (Results 1 – 25 of 640) sorted by relevance

12345678910>>...26

/Linux-v6.1/arch/arm/kernel/
Dsmp_tlb.c106 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
110 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
112 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
117 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
/Linux-v6.1/Documentation/process/
Ddeprecated.rst58 risk of them overflowing. This could lead to values wrapping around and a
60 allocations could lead to linear overflows of heap memory and other
116 explicitly ignore overflows, which may lead to unexpected results
137 be NUL terminated. This can lead to various linear read overflows and
160 size limit. This is both inefficient and can lead to linear read overflows
167 Traditionally, using "%p" in format strings would lead to regular address
196 lead to a crash, possible overwriting sensitive contents at the end of the
D7.AdvancedTopics.rst79 Excessive use of this capability can lead to other problems, though, beyond
177 All types of review, if they lead to better code going into the kernel, are
/Linux-v6.1/arch/mips/include/asm/
Dcompiler.h17 * that can lead to instructions from beyond an unreachable statement being
19 * is the only content of a case in a switch statement. This can lead to
/Linux-v6.1/Documentation/hwmon/
Dadm1026.rst96 voltage from the power lead rather than on the ground lead.
/Linux-v6.1/Documentation/kbuild/
Dreproducible-builds.rst125 Uncommitted changes or different commit ids in git can also lead
129 will be different, which will eventually lead to binary differences.
/Linux-v6.1/Documentation/ABI/obsolete/
Dsysfs-firmware-acpi7 the offline failure might lead to memory corruption and crashes)
/Linux-v6.1/drivers/media/pci/ivtv/
Divtvfb.c379 u16 lead = 0, tail = 0; in ivtvfb_write() local
414 lead = 4 - ((unsigned long)dst & 3); in ivtvfb_write()
415 if (copy_from_user(dst, buf, lead)) in ivtvfb_write()
417 buf += lead; in ivtvfb_write()
418 dst += lead; in ivtvfb_write()
421 if ((count - lead) & 3) in ivtvfb_write()
422 tail = (count - lead) & 3; in ivtvfb_write()
424 dma_size = count - lead - tail; in ivtvfb_write()
426 p + lead + dma_offset, (void __user *)buf, dma_size); in ivtvfb_write()
/Linux-v6.1/drivers/clk/qcom/
Dclk-regmap-phy-mux.h18 * which in turn would lead to disabling corresponding pipe_clk_src (and thus
/Linux-v6.1/arch/arm64/boot/dts/allwinner/
Dsun50i-a64-pinephone-1.1.dts17 * 1.0, and the lowest PWM duty cycle that doesn't lead to backlight
Dsun50i-a64-pinephone-1.2.dts22 * and the lowest PWM duty cycle that doesn't lead to backlight being off
/Linux-v6.1/arch/powerpc/mm/book3s64/
DMakefile25 # Instrumenting the SLB fault path can lead to duplicate SLB entries
/Linux-v6.1/drivers/media/pci/ddbridge/
DKconfig40 might lead to I2C errors originating from the bridge in conjunction
/Linux-v6.1/arch/x86/include/asm/
Dacenv.h22 * sleep state and cannot lead to data loss.
/Linux-v6.1/net/dsa/
Dtag_hellcreek.c25 * avoid including it in calculations. That would lead to wrong in hellcreek_xmit()
/Linux-v6.1/Documentation/devicetree/bindings/display/mediatek/
Dmediatek,ufoe.yaml15 UFOe can cut the data rate for DSI port which may lead to reduce power
/Linux-v6.1/Documentation/devicetree/bindings/media/i2c/
Dadv7343.txt3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
/Linux-v6.1/drivers/gpu/drm/i915/
Di915_switcheroo.c43 * FIXME: open_count is protected by drm_global_mutex but that would lead to in i915_switcheroo_can_switch()
/Linux-v6.1/include/net/
Dcls_cgroup.h59 * would lead to false results. in task_get_classid()
/Linux-v6.1/drivers/eisa/
DKconfig48 # an X86 may lead to crashes...
/Linux-v6.1/Documentation/devicetree/bindings/sound/
Dcirrus,cs4234.yaml22 provide lead time for the external switch-mode power supply, and a
/Linux-v6.1/arch/arm/
DKconfig688 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
726 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
732 optimisation in the Cortex-A9 Store Buffer may lead to data
810 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
846 lead to either a data corruption or a CPU deadlock. Not fixed in
853 bool "ARM errata: A12: sequence of VMOV to core registers might lead to a dead lock"
859 one is in the shadow of a branch or abort, can lead to a
894 lead to either a data corruption or a CPU deadlock. Not fixed in
/Linux-v6.1/drivers/net/ethernet/ibm/ehea/
Dehea_qmr.h145 /* Defines which bad send cqe stati lead to a port reset */
185 /* Defines which affiliated errors lead to a port reset */
/Linux-v6.1/Documentation/driver-api/md/
Draid5-ppl.rst9 disks is missing. This can lead to silent data corruption when rebuilding the
/Linux-v6.1/security/tomoyo/
DKconfig49 operations which can lead to the hijacking of the boot sequence are

12345678910>>...26