Home
last modified time | relevance | path

Searched refs:incorrect (Results 1 – 25 of 101) sorted by relevance

12345

/Linux-v6.1/kernel/trace/
Dtrace_branch.c227 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.1/Documentation/devicetree/bindings/mmc/
Dsdhci.txt7 - 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.1/arch/loongarch/
DKconfig.debug14 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.1/drivers/atm/
Dnicstar.h580 #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.1/arch/m68k/fpsp040/
Dx_operr.S162 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.1/Documentation/userspace-api/media/dvb/
Ddmx-munmap.rst51 The ``start`` or ``length`` is incorrect, or no buffers have been
/Linux-v6.1/Documentation/userspace-api/media/v4l/
Dfunc-munmap.rst53 The ``start`` or ``length`` is incorrect, or no buffers have been
/Linux-v6.1/arch/arm/boot/dts/
Dberlin2cd-google-chromecast.dts28 * with this device provides an incorrect memory range in
Dbcm53016-meraki-mr32.dts133 * It will only detect the "nvram" partition with an incorrect size.
/Linux-v6.1/Documentation/pcmcia/
Ddevicetable.rst23 If the hash is incorrect, the kernel will inform you about this in "dmesg"
/Linux-v6.1/drivers/staging/qlge/
DTODO7 * truesize accounting is incorrect (ex: a 9000B frame has skb->truesize 10280
/Linux-v6.1/Documentation/devicetree/bindings/sound/
Dtlv320aic3x.txt27 If this node is not mentioned or if the value is incorrect, then MicBias
/Linux-v6.1/include/linux/
Dcompiler_types.h123 unsigned long incorrect; member
/Linux-v6.1/Documentation/devicetree/bindings/net/
Dmicrel-ksz90x1.txt18 incorrect values came from an error in the original KSZ9021 datasheet
227 still reflects that incorrect document.
/Linux-v6.1/Documentation/userspace-api/
Dspec_ctrl.rst80 ERANGE arg3 is incorrect, i.e. it's neither PR_SPEC_ENABLE nor
/Linux-v6.1/Documentation/driver-api/md/
Draid5-ppl.rst12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
/Linux-v6.1/arch/m68k/math-emu/
Dfp_entry.S112 | instruction decoding, otherwise the stack pointer is incorrect
/Linux-v6.1/tools/perf/Documentation/
Dperf-c2c.txt125 where it creates incorrect call stacks from incorrect matches.
/Linux-v6.1/Documentation/dev-tools/
Dkmsan.rst95 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.1/Documentation/filesystems/
Docfs2-online-filecheck.rst28 In case of directory to file links is incorrect, the directory inode is
/Linux-v6.1/tools/testing/selftests/cgroup/
Dtest_cpuset_prs.sh654 echo "FAILED: Inotify test - incorrect state"
/Linux-v6.1/Documentation/networking/
Dila.rst117 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.1/arch/arm64/
DKconfig527 bool "Cortex-A53: 845719: a load might read incorrect data"
537 might return incorrect data.
548 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
554 cause subsequent memory accesses to use an incorrect address on
563 …tex-A55: 1024718: Update of DBM/AP bits without break before make might result in incorrect update"
568 Affected Cortex-A55 cores (all revisions) could cause incorrect
577 …-N1: MRC read following MRRC read of specific Generic Timer in AArch32 might give incorrect result"
594 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
607 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
620 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
[all …]
/Linux-v6.1/drivers/virtio/
DKconfig163 or module parameters. Be aware that using incorrect parameters (base
/Linux-v6.1/arch/powerpc/platforms/8xx/
DKconfig116 This bug can cause incorrect code execution under certain

12345