Home
last modified time | relevance | path

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

/linux-4.4.14/kernel/trace/
Dtrace_branch.c217 f->incorrect++; in ftrace_likely_update()
240 percent = p->incorrect * 100; in get_incorrect_percent()
241 percent /= p->correct + p->incorrect; in get_incorrect_percent()
243 percent = p->incorrect ? 100 : -1; in get_incorrect_percent()
265 seq_printf(m, "%8lu %8lu ", p->correct, p->incorrect); in branch_stat_show()
307 if (a->incorrect < b->incorrect) in annotated_branch_stat_cmp()
309 if (a->incorrect > b->incorrect) in annotated_branch_stat_cmp()
/linux-4.4.14/drivers/staging/rdma/hfi1/
DTODO6 - Replace incorrect uAPI
/linux-4.4.14/drivers/atm/
Dnicstar.h579 #error NS_SMBUFSIZE is incorrect in nicstar.h
591 #error NS_LGBUFSIZE is incorrect in nicstar.h
601 #error NS_RSQSIZE is incorrect in nicstar.h
613 #error NS_VPIBITS is incorrect in nicstar.h
/linux-4.4.14/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-4.4.14/arch/parisc/
DKconfig.debug10 in order to catch accidental (and incorrect) writes to such const
/linux-4.4.14/mm/
DKconfig.debug26 that would result in incorrect warnings of memory corruption after
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dtlv320aic3x.txt27 If this node is not mentioned or if the value is incorrect, then MicBias
/linux-4.4.14/Documentation/pcmcia/
Ddevicetable.txt19 If the hash is incorrect, the kernel will inform you about this in "dmesg"
/linux-4.4.14/Documentation/isdn/
DREADME.pcbit19 - The board reset procedure is at the moment incorrect and will only
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Darm,gic.txt133 - arm,msi-base-spi : When the MSI_TYPER register contains an incorrect
137 - arm,msi-num-spis : When the MSI_TYPER register contains an incorrect
/linux-4.4.14/Documentation/devicetree/bindings/serial/
D8250.txt52 erratum A-004737 (relating to incorrect BRK handling).
/linux-4.4.14/drivers/virtio/
DKconfig76 or module parameters. Be aware that using incorrect parameters (base
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Ddwc3.txt48 fladj_30mhz_sdbnd signal is invalid or incorrect.
/linux-4.4.14/arch/arm/boot/dts/
Dtegra20-paz00.dts398 * name is incorrect; perhaps copied
399 * from an incorrect NVIDIA reference.
/linux-4.4.14/include/linux/
Dcompiler.h92 unsigned long incorrect; member
/linux-4.4.14/arch/m68k/math-emu/
Dfp_entry.S112 | instruction decoding, otherwise the stack pointer is incorrect
/linux-4.4.14/arch/powerpc/platforms/8xx/
DKconfig136 This bug can cause incorrect code execution under certain
/linux-4.4.14/arch/arm64/
DKconfig341 bool "Cortex-A53: 845719: a load might read incorrect data"
351 might return incorrect data.
362 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
368 a subsequent memory access to use an incorrect address on Cortex-A53
/linux-4.4.14/Documentation/scsi/
DChangeLog.arcmsr40 ** 1.20.00.11 9/29/2005 Erich Chen by comment of Arjan van de Ven fix incorrect msleep…
Din2000.txt26 Fixed a bug that caused incorrect SCSI status bytes to be
DChangeLog.lpfc273 of ulpPU and fcpi_parm to avoid incorrect read check of Write IO
274 and incorrect read length.
/linux-4.4.14/Documentation/early-userspace/
Dbuffer-format.txt77 clearly incorrect (a cyclic redundancy check is a different and
/linux-4.4.14/Documentation/x86/i386/
DIO-APIC.txt102 'incorrect' pirq line will cause the booting process to hang, or a device
/linux-4.4.14/Documentation/driver-model/
Doverview.txt59 and to discourage meaningless and incorrect casts between the two.
/linux-4.4.14/Documentation/networking/
Dskfp.txt190 - Interrupt routing on SMP machines could be incorrect
Dcxgb.txt239 2. After running insmod, the driver is loaded and the incorrect network
253 network card, your new interface will have incorrect IP address and
De100.txt79 NOTE: setting the speed/duplex to incorrect values will cause the link to
D3c509.txt152 likely have an unterminated network or the incorrect media transceiver selected.
Darcnet-hardware.txt723 off | defective board or | incorrect memory or
950 off | defective board or | incorrect memory or
Dfilter.txt1220 accesses the memory with incorrect alignment:
/linux-4.4.14/Documentation/i2c/
Dfault-codes54 on these as the only way to detect incorrect data transfers.
/linux-4.4.14/Documentation/block/
Dbiovecs.txt95 * Almost all usage of bi_idx is now incorrect and has been removed; instead,
/linux-4.4.14/Documentation/
Dsvga.txt201 When the mode detection doesn't work (e.g., the mode list is incorrect or
216 contains the most common video BIOS bug called "incorrect vertical display
Dkobject.txt30 up and incorrect, and your code will be buggy. So do not do this.
146 incorrect and needs to be fixed.
Dkprobes.txt460 If the functions find an incorrect probe (ex. an unregistered probe),
491 If the functions find some incorrect probes (ex. unregistered
493 incorrect probes. However, other probes in the array are
Drobust-futexes.txt95 is empty. If the thread/process crashed or terminated in some incorrect
Dintel_txt.txt97 incorrect), it will directly launch the kernel with no changes
DDMA-API-HOWTO.txt559 from panics to silent data corruption. A couple of examples of incorrect ways
Dkernel-parameters.txt937 panels may send no or incorrect EDID data sets.
1988 significantly divergent settings. An incorrect value
Dmemory-barriers.txt960 Apparently incorrect ---> | | B->7 |------>| |
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES535 Fix incorrect file size in file handle based setattr on big endian hardware.
774 Fixed various incorrect or misleading smb to posix error code mappings.
796 incorrect resume key).
949 Fix intermittent problem with incorrect smb header checking on badly
978 Various FindNext fixes for incorrect filenames on large directory searches on big endian
1002 it. Fixed a few bugs in the DFS code (e.g. bcc two bytes too short and incorrect uid in PDU).
DREADME347 coherency checks (i.e. incorrect attribute cache for a short
/linux-4.4.14/Documentation/video4linux/
Duvcvideo.txt224 The specified buffer size is incorrect (too big or too small).
/linux-4.4.14/Documentation/filesystems/caching/
Dcachefiles.txt176 serve incorrect data.
307 any file of an incorrect type (such as a FIFO file or a device file).
/linux-4.4.14/Documentation/s390/
Dcds.txt250 CCW_FLAG_SLI - suppress incorrect length
311 SCHN_STAT_INCORR_LEN - incorrect length
/linux-4.4.14/arch/arm/
DKconfig1033 bool "ARM errata: FSR write bit incorrect on a SWP to read-only memory"
1060 executing the new code sequence in the incorrect ARM or Thumb state.
1122 bool "ARM errata: LoUIS bit field in CLIDR register is incorrect"
1238 bool "ARM errata: incorrect instructions may be executed from loop buffer"
1243 loop buffer may deliver incorrect instructions. This
/linux-4.4.14/arch/m68k/
DKconfig.cpu315 mantissa and round slightly incorrect, what is more than enough
/linux-4.4.14/Documentation/fb/
Dframebuffer.txt152 work 100% with XF68_FBDev: the reported clock values are always incorrect.
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt170 incorrect data. To prevent this, we introduce the RTT.
/linux-4.4.14/Documentation/x86/x86_64/
Dboot-options.txt83 problems with incorrect timer initialization on some boards.
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-tape.1995-2002135 * MTTELL was sometimes returning incorrect results.
/linux-4.4.14/arch/x86/
DKconfig.debug100 in order to catch accidental (and incorrect) writes to such const
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dpfpsp.S963 # underflow exception. Since this is incorrect, we need to check
3091 # input operand in the fsave frame may be incorrect for some cases #
3761 # be incorrect for some cases and need to be adjusted. So, this package #
3949 # stacked for the exception is incorrect for -(an) and (an)+ addressing #
Dfpsp.S964 # underflow exception. Since this is incorrect, we need to check
3092 # input operand in the fsave frame may be incorrect for some cases #
3762 # be incorrect for some cases and need to be adjusted. So, this package #
/linux-4.4.14/scripts/dtc/
Ddtc-parser.tab.c_shipped287 /* Suppress an incorrect diagnostic about yylval being uninitialized. */
2026 incorrect destructor might then be invoked immediately. In the
2028 to an incorrect destructor call or verbose syntax error message
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-pci292 source. If that is missing or incorrect, this file can be
/linux-4.4.14/Documentation/RCU/
Dtorture.txt177 "rcu_busted": This tests an intentionally incorrect version
/linux-4.4.14/scripts/genksyms/
Dparse.tab.c_shipped2168 incorrect destructor might then be invoked immediately. In the
2170 to an incorrect destructor call or verbose syntax error message
/linux-4.4.14/drivers/mtd/nand/
DKconfig187 incorrect ECC generation, and if using these, the default of
/linux-4.4.14/Documentation/filesystems/
Dpath-lookup.txt115 lookup of the old list veering off into the new (incorrect) list and missing
Dext4.txt400 mode - metadata journaling. A crash+recovery can cause incorrect data to
Dproc.txt92 complaining about how you screwed up your system because of incorrect
/linux-4.4.14/scripts/kconfig/
Dzconf.tab.c_shipped2111 incorrect destructor might then be invoked immediately. In the
2113 to an incorrect destructor call or verbose syntax error message
/linux-4.4.14/Documentation/trace/
Dring-buffer-design.txt943 the reader from seeing the incorrect head page.
/linux-4.4.14/Documentation/development-process/
D4.Coding363 out. Anything which might tempt a code janitor to make an incorrect
/linux-4.4.14/Documentation/arm64/
Darm-acpi.txt140 the ACPI signature "RSD PTR "). If this pointer is incorrect and acpi=force
/linux-4.4.14/lib/
DKconfig.debug964 bool "Lock debugging: detect incorrect freeing of live locks"
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt905 "line" size here which is incorrect. The kernel will prefer the cache