Home
last modified time | relevance | path

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

12345

/linux/kernel/trace/
A 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/Documentation/devicetree/bindings/mmc/
A 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/drivers/atm/
A 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/Documentation/devicetree/bindings/arm/
A Dgemini.yaml83 - description: Wiligear Wiliboard WBD-111 - old incorrect binding
89 - description: Wiligear Wiliboard WBD-222 - old incorrect binding
/linux/arch/m68k/fpsp040/
A 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/Documentation/userspace-api/media/dvb/
A Ddmx-munmap.rst51 The ``start`` or ``length`` is incorrect, or no buffers have been
/linux/Documentation/userspace-api/media/v4l/
A Dfunc-munmap.rst53 The ``start`` or ``length`` is incorrect, or no buffers have been
/linux/arch/arm/boot/dts/
A Dberlin2cd-google-chromecast.dts28 * with this device provides an incorrect memory range in
A Dbcm53016-meraki-mr32.dts169 * It will only detect the "nvram" partition with an incorrect size.
A Dtegra20-paz00.dts467 * name is incorrect; perhaps copied
468 * from an incorrect NVIDIA reference.
/linux/Documentation/pcmcia/
A Ddevicetable.rst23 If the hash is incorrect, the kernel will inform you about this in "dmesg"
/linux/Documentation/devicetree/bindings/interrupt-controller/
A Darm,gic.yaml168 description: When the MSI_TYPER register contains an incorrect value,
174 description: When the MSI_TYPER register contains an incorrect value,
/linux/drivers/staging/qlge/
A DTODO7 * truesize accounting is incorrect (ex: a 9000B frame has skb->truesize 10280
/linux/Documentation/devicetree/bindings/sound/
A Dtlv320aic3x.txt27 If this node is not mentioned or if the value is incorrect, then MicBias
/linux/include/linux/
A Dcompiler_types.h109 unsigned long incorrect; member
/linux/Documentation/devicetree/bindings/net/
A Dmicrel-ksz90x1.txt18 incorrect values came from an error in the original KSZ9021 datasheet
227 still reflects that incorrect document.
/linux/Documentation/userspace-api/
A Dspec_ctrl.rst80 ERANGE arg3 is incorrect, i.e. it's neither PR_SPEC_ENABLE nor
/linux/Documentation/devicetree/bindings/spi/
A Dsprd,spi-adi.yaml38 ADI registers will make ADI controller registers chaos to lead incorrect results.
/linux/tools/perf/Documentation/
A Dperf-c2c.txt121 where it creates incorrect call stacks from incorrect matches.
/linux/Documentation/driver-api/md/
A Draid5-ppl.rst12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
/linux/arch/m68k/math-emu/
A Dfp_entry.S112 | instruction decoding, otherwise the stack pointer is incorrect
/linux/Documentation/networking/
A 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/arch/arm64/
A DKconfig492 bool "Cortex-A53: 845719: a load might read incorrect data"
502 might return incorrect data.
513 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
519 cause subsequent memory accesses to use an incorrect address on
528 …tex-A55: 1024718: Update of DBM/AP bits without break before make might result in incorrect update"
533 Affected Cortex-A55 cores (all revisions) could cause incorrect
542 …-N1: MRC read following MRRC read of specific Generic Timer in AArch32 might give incorrect result"
559 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
572 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
585 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
[all …]
/linux/drivers/virtio/
A DKconfig149 or module parameters. Be aware that using incorrect parameters (base
/linux/Documentation/filesystems/
A Docfs2-online-filecheck.rst28 In case of directory to file links is incorrect, the directory inode is

Completed in 37 milliseconds

12345