Searched refs:incorrect (Results 1 – 25 of 105) sorted by relevance
12345
| /Linux-v6.6/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-v6.6/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-v6.6/arch/loongarch/ |
| D | Kconfig.debug | 14 finds. Some of the addresses it reports may be incorrect.
26 Some of the addresses it reports may be incorrect (but better than the
|
| /Linux-v6.6/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-v6.6/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-v6.6/Documentation/userspace-api/media/dvb/ |
| D | dmx-munmap.rst | 51 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| /Linux-v6.6/Documentation/userspace-api/media/v4l/ |
| D | func-munmap.rst | 53 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| /Linux-v6.6/arch/arm/boot/dts/synaptics/ |
| D | berlin2cd-google-chromecast.dts | 28 * with this device provides an incorrect memory range in
|
| /Linux-v6.6/Documentation/pcmcia/ |
| D | devicetable.rst | 23 If the hash is incorrect, the kernel will inform you about this in "dmesg"
|
| /Linux-v6.6/drivers/staging/qlge/ |
| D | TODO | 7 * truesize accounting is incorrect (ex: a 9000B frame has skb->truesize 10280
|
| /Linux-v6.6/arch/arm/boot/dts/broadcom/ |
| D | bcm53016-meraki-mr32.dts | 131 * It will only detect the "nvram" partition with an incorrect size.
|
| D | bcm47094-dlink-dir-890l.dts | 147 * assume. The CFE loader contains incorrect information
|
| /Linux-v6.6/Documentation/devicetree/bindings/net/ |
| D | micrel-ksz90x1.txt | 18 incorrect values came from an error in the original KSZ9021 datasheet
228 still reflects that incorrect document.
|
| /Linux-v6.6/Documentation/userspace-api/ |
| D | spec_ctrl.rst | 80 ERANGE arg3 is incorrect, i.e. it's neither PR_SPEC_ENABLE nor
|
| /Linux-v6.6/include/linux/ |
| D | compiler_types.h | 177 unsigned long incorrect; member
|
| /Linux-v6.6/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
|
| /Linux-v6.6/arch/m68k/math-emu/ |
| D | fp_entry.S | 112 | instruction decoding, otherwise the stack pointer is incorrect
|
| /Linux-v6.6/Documentation/dev-tools/ |
| D | kmsan.rst | 95 incorrect shadow/origin values, likely leading to false positives. Functions
96 called from non-instrumented code may also receive incorrect metadata for their
389 corrupt other pages or read incorrect values from them.
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 28 In case of directory to file links is incorrect, the directory inode is
|
| /Linux-v6.6/tools/testing/selftests/cgroup/ |
| D | test_cpuset_prs.sh | 672 echo "FAILED: Inotify test - incorrect state"
|
| /Linux-v6.6/Documentation/networking/ |
| D | ila.rst | 117 incorrect on the wire. This is a problem for intermediate devices,
121 - no action Allow the checksum to be incorrect on the wire. Before
|
| /Linux-v6.6/tools/perf/Documentation/ |
| D | perf-c2c.txt | 129 where it creates incorrect call stacks from incorrect matches.
|
| /Linux-v6.6/arch/arm64/ |
| D | Kconfig | 585 bool "Cortex-A53: 845719: a load might read incorrect data"
595 might return incorrect data.
606 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
611 cause subsequent memory accesses to use an incorrect address on
620 …tex-A55: 1024718: Update of DBM/AP bits without break before make might result in incorrect update"
625 Affected Cortex-A55 cores (all revisions) could cause incorrect
634 …-N1: MRC read following MRRC read of specific Generic Timer in AArch32 might give incorrect result"
651 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
664 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
677 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
[all …]
|
| /Linux-v6.6/Documentation/core-api/ |
| D | packing.rst | 163 programmer against incorrect API use. The errors are not expected to occur
|
| /Linux-v6.6/drivers/virtio/ |
| D | Kconfig | 163 or module parameters. Be aware that using incorrect parameters (base
|
12345
