Searched refs:incorrect (Results 1 – 25 of 88) sorted by relevance
1234
| /Linux-v5.4/kernel/trace/ |
| D | trace_branch.c | 227 f->data.incorrect++; in ftrace_likely_update()
252 percent = p->incorrect * 100; in get_incorrect_percent()
253 percent /= p->correct + p->incorrect; in get_incorrect_percent()
255 percent = p->incorrect ? 100 : -1; in get_incorrect_percent()
292 seq_printf(m, "%8lu %8lu ", p->correct, p->incorrect); in branch_stat_show_normal()
312 p->data.correct, p->constant, l, p->data.incorrect); in annotate_branch_stat_show()
350 if (a->incorrect < b->incorrect) in annotated_branch_stat_cmp()
352 if (a->incorrect > b->incorrect) in annotated_branch_stat_cmp()
|
| /Linux-v5.4/Documentation/devicetree/bindings/mmc/ |
| D | sdhci.txt | 7 - sdhci-caps-mask: The sdhci capabilities register is incorrect. This 64bit
9 is on in the mask then the bit is incorrect in the register and should be
11 - sdhci-caps: The sdhci capabilities register is incorrect. This 64bit
|
| /Linux-v5.4/drivers/atm/ |
| D | nicstar.h | 580 #error NS_SMBUFSIZE is incorrect in nicstar.h
592 #error NS_LGBUFSIZE is incorrect in nicstar.h
602 #error NS_RSQSIZE is incorrect in nicstar.h
614 #error NS_VPIBITS is incorrect in nicstar.h
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | x_operr.S | 162 bnes chkwerr |if not equal, check for incorrect operr
165 bnes chkwerr |if d0 is true, check for incorrect operr
189 bnes chkberr |if not equal, check for incorrect operr
192 bnes chkberr |if d0 is true, check for incorrect operr
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | berlin2cd-google-chromecast.dts | 28 * with this device provides an incorrect memory range in
|
| D | tegra20-paz00.dts | 403 * name is incorrect; perhaps copied
404 * from an incorrect NVIDIA reference.
|
| /Linux-v5.4/Documentation/media/uapi/dvb/ |
| D | dmx-munmap.rst | 62 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| /Linux-v5.4/Documentation/pcmcia/ |
| D | devicetable.rst | 23 If the hash is incorrect, the kernel will inform you about this in "dmesg"
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | tlv320aic3x.txt | 27 If this node is not mentioned or if the value is incorrect, then MicBias
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | func-munmap.rst | 64 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| /Linux-v5.4/include/linux/ |
| D | compiler_types.h | 92 unsigned long incorrect; member
|
| /Linux-v5.4/Documentation/devicetree/bindings/thermal/ |
| D | imx-thermal.txt | 23 Direct access to OCOTP via fsl,tempmon-data is incorrect on some newer chips
|
| /Linux-v5.4/drivers/staging/qlge/ |
| D | TODO | 10 * truesize accounting is incorrect (ex: a 9000B frame has skb->truesize 10280
|
| /Linux-v5.4/drivers/virtio/ |
| D | Kconfig | 92 or module parameters. Be aware that using incorrect parameters (base
|
| /Linux-v5.4/Documentation/userspace-api/ |
| D | spec_ctrl.rst | 80 ERANGE arg3 is incorrect, i.e. it's neither PR_SPEC_ENABLE nor
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | battery.txt | 6 no appropriate non-volatile memory, or it is unprogrammed/incorrect.
|
| /Linux-v5.4/Documentation/devicetree/bindings/serial/ |
| D | 8250.txt | 65 erratum A-004737 (relating to incorrect BRK handling).
|
| /Linux-v5.4/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
|
| /Linux-v5.4/Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 25 ADI registers will make ADI controller registers chaos to lead incorrect results.
|
| /Linux-v5.4/arch/m68k/math-emu/ |
| D | fp_entry.S | 112 | instruction decoding, otherwise the stack pointer is incorrect
|
| /Linux-v5.4/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 125 This bug can cause incorrect code execution under certain
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | ocfs2-online-filecheck.txt | 25 In case of directory to file links is incorrect, the directory inode is
|
| /Linux-v5.4/Documentation/networking/ |
| D | ila.txt | 108 incorrect on the wire. This is a problem for intermediate devices,
112 - no action Allow the checksum to be incorrect on the wire. Before
|
| /Linux-v5.4/arch/arm64/ |
| D | Kconfig | 453 bool "Cortex-A53: 845719: a load might read incorrect data"
463 might return incorrect data.
474 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
480 cause subsequent memory accesses to use an incorrect address on
486 …tex-A55: 1024718: Update of DBM/AP bits without break before make might result in incorrect update"
491 Affected Cortex-A55 cores (r0p0, r0p1, r1p0) could cause incorrect
500 …-N1: MRC read following MRRC read of specific Generic Timer in AArch32 might give incorrect result"
514 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
640 On Falkor v1, an incorrect ASID may be cached in the TLB when ASID
|
| /Linux-v5.4/Documentation/driver-api/early-userspace/ |
| D | buffer-format.rst | 83 clearly incorrect (a cyclic redundancy check is a different and
|
1234
