Searched full:lead (Results 1 – 25 of 640) sorted by relevance
12345678910>>...26
/Linux-v6.1/arch/arm/kernel/ |
D | smp_tlb.c | 106 * 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/ |
D | deprecated.rst | 58 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
|
D | 7.AdvancedTopics.rst | 79 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/ |
D | compiler.h | 17 * 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/ |
D | adm1026.rst | 96 voltage from the power lead rather than on the ground lead.
|
/Linux-v6.1/Documentation/kbuild/ |
D | reproducible-builds.rst | 125 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/ |
D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
/Linux-v6.1/drivers/media/pci/ivtv/ |
D | ivtvfb.c | 379 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/ |
D | clk-regmap-phy-mux.h | 18 * which in turn would lead to disabling corresponding pipe_clk_src (and thus
|
/Linux-v6.1/arch/arm64/boot/dts/allwinner/ |
D | sun50i-a64-pinephone-1.1.dts | 17 * 1.0, and the lowest PWM duty cycle that doesn't lead to backlight
|
D | sun50i-a64-pinephone-1.2.dts | 22 * and the lowest PWM duty cycle that doesn't lead to backlight being off
|
/Linux-v6.1/arch/powerpc/mm/book3s64/ |
D | Makefile | 25 # Instrumenting the SLB fault path can lead to duplicate SLB entries
|
/Linux-v6.1/drivers/media/pci/ddbridge/ |
D | Kconfig | 40 might lead to I2C errors originating from the bridge in conjunction
|
/Linux-v6.1/arch/x86/include/asm/ |
D | acenv.h | 22 * sleep state and cannot lead to data loss.
|
/Linux-v6.1/net/dsa/ |
D | tag_hellcreek.c | 25 * avoid including it in calculations. That would lead to wrong in hellcreek_xmit()
|
/Linux-v6.1/Documentation/devicetree/bindings/display/mediatek/ |
D | mediatek,ufoe.yaml | 15 UFOe can cut the data rate for DSI port which may lead to reduce power
|
/Linux-v6.1/Documentation/devicetree/bindings/media/i2c/ |
D | adv7343.txt | 3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
|
/Linux-v6.1/drivers/gpu/drm/i915/ |
D | i915_switcheroo.c | 43 * FIXME: open_count is protected by drm_global_mutex but that would lead to in i915_switcheroo_can_switch()
|
/Linux-v6.1/include/net/ |
D | cls_cgroup.h | 59 * would lead to false results. in task_get_classid()
|
/Linux-v6.1/drivers/eisa/ |
D | Kconfig | 48 # an X86 may lead to crashes...
|
/Linux-v6.1/Documentation/devicetree/bindings/sound/ |
D | cirrus,cs4234.yaml | 22 provide lead time for the external switch-mode power supply, and a
|
/Linux-v6.1/arch/arm/ |
D | Kconfig | 688 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/ |
D | ehea_qmr.h | 145 /* 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/ |
D | raid5-ppl.rst | 9 disks is missing. This can lead to silent data corruption when rebuilding the
|
/Linux-v6.1/security/tomoyo/ |
D | Kconfig | 49 operations which can lead to the hijacking of the boot sequence are
|
12345678910>>...26