Home
last modified time | relevance | path

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

12345

/linux-6.15/kernel/trace/
H A Dtrace_branch.c223 f->data.incorrect++; in ftrace_likely_update()
248 percent = p->incorrect * 100; in get_incorrect_percent()
249 percent /= p->correct + p->incorrect; in get_incorrect_percent()
251 percent = p->incorrect ? 100 : -1; in get_incorrect_percent()
288 seq_printf(m, "%8lu %8lu ", p->correct, p->incorrect); in branch_stat_show_normal()
308 p->data.correct, p->constant, l, p->data.incorrect); in annotate_branch_stat_show()
346 if (a->incorrect < b->incorrect) in annotated_branch_stat_cmp()
348 if (a->incorrect > b->incorrect) in annotated_branch_stat_cmp()
/linux-6.15/Documentation/devicetree/bindings/mmc/
H 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-6.15/arch/loongarch/
H A 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-6.15/drivers/atm/
H 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-6.15/Documentation/devicetree/bindings/arm/
H A Dgemini.yaml83 - description: Wiligear Wiliboard WBD-111 - old incorrect binding
89 - description: Wiligear Wiliboard WBD-222 - old incorrect binding
/linux-6.15/arch/m68k/fpsp040/
H 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-6.15/Documentation/userspace-api/media/dvb/
H A Ddmx-munmap.rst51 The ``start`` or ``length`` is incorrect, or no buffers have been
/linux-6.15/Documentation/userspace-api/media/v4l/
H A Dfunc-munmap.rst53 The ``start`` or ``length`` is incorrect, or no buffers have been
/linux-6.15/arch/arm/boot/dts/synaptics/
H A Dberlin2cd-google-chromecast.dts28 * with this device provides an incorrect memory range in
/linux-6.15/Documentation/pcmcia/
H A Ddevicetable.rst23 If the hash is incorrect, the kernel will inform you about this in "dmesg"
/linux-6.15/arch/arm64/boot/dts/rockchip/
H A Drk3588-jaguar-pre-ict-tester.dtso78 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
100 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
/linux-6.15/Documentation/devicetree/bindings/interrupt-controller/
H A Darm,gic.yaml169 description: When the MSI_TYPER register contains an incorrect value,
175 description: When the MSI_TYPER register contains an incorrect value,
H A Dfsl,ls-extirq.yaml108 # incorrect position. Remove interrupt-map restriction because it always
/linux-6.15/Documentation/process/debugging/
H A Dindex.rst70 consistently (i.e. given a set of inputs you always get the same, incorrect
/linux-6.15/arch/arm/boot/dts/broadcom/
H A Dbcm53016-meraki-mr32.dts131 * It will only detect the "nvram" partition with an incorrect size.
H A Dbcm47094-dlink-dir-890l.dts147 * assume. The CFE loader contains incorrect information
/linux-6.15/Documentation/devicetree/bindings/net/
H A Dmicrel-ksz90x1.txt18 incorrect values came from an error in the original KSZ9021 datasheet
228 still reflects that incorrect document.
H A Dethernet-phy.yaml38 If the PHY reports an incorrect ID (or none at all) then the
171 device tree due to limitations in hardware strapping or incorrect strap
/linux-6.15/Documentation/userspace-api/
H A Dspec_ctrl.rst80 ERANGE arg3 is incorrect, i.e. it's neither PR_SPEC_ENABLE nor
/linux-6.15/Documentation/devicetree/bindings/spi/
H A Dsprd,spi-adi.yaml37 ADI registers will make ADI controller registers chaos to lead incorrect results.
/linux-6.15/Documentation/driver-api/md/
H A Draid5-ppl.rst12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
/linux-6.15/include/linux/
H A Dcompiler_types.h198 unsigned long incorrect; member
/linux-6.15/arch/m68k/math-emu/
H A Dfp_entry.S112 | instruction decoding, otherwise the stack pointer is incorrect
/linux-6.15/Documentation/dev-tools/
H A 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
396 corrupt other pages or read incorrect values from them.
/linux-6.15/Documentation/devicetree/bindings/
H A Dincomplete-devices.yaml283 - broken-usage-of-incorrect-compatible

12345