| /linux-4.1.27/kernel/trace/ |
| D | trace_branch.c | 228 f->incorrect++; in ftrace_likely_update()
251 percent = p->incorrect * 100; in get_incorrect_percent()
252 percent /= p->correct + p->incorrect; in get_incorrect_percent()
254 percent = p->incorrect ? 100 : -1; in get_incorrect_percent()
276 seq_printf(m, "%8lu %8lu ", p->correct, p->incorrect); in branch_stat_show()
318 if (a->incorrect < b->incorrect) in annotated_branch_stat_cmp()
320 if (a->incorrect > b->incorrect) in annotated_branch_stat_cmp()
|
| /linux-4.1.27/drivers/atm/ |
| D | nicstar.h | 579 #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.1.27/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-4.1.27/arch/parisc/ |
| D | Kconfig.debug | 10 in order to catch accidental (and incorrect) writes to such const
|
| /linux-4.1.27/mm/ |
| D | Kconfig.debug | 26 that would result in incorrect warnings of memory corruption after
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | tlv320aic3x.txt | 27 If this node is not mentioned or if the value is incorrect, then MicBias
|
| /linux-4.1.27/Documentation/pcmcia/ |
| D | devicetable.txt | 19 If the hash is incorrect, the kernel will inform you about this in "dmesg"
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | gic.txt | 117 - arm,msi-base-spi : When the MSI_TYPER register contains an incorrect
121 - arm,msi-num-spis : When the MSI_TYPER register contains an incorrect
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.pcbit | 19 - The board reset procedure is at the moment incorrect and will only
|
| /linux-4.1.27/Documentation/devicetree/bindings/serial/ |
| D | 8250.txt | 52 erratum A-004737 (relating to incorrect BRK handling).
|
| /linux-4.1.27/drivers/virtio/ |
| D | Kconfig | 76 or module parameters. Be aware that using incorrect parameters (base
|
| /linux-4.1.27/include/linux/ |
| D | compiler.h | 90 unsigned long incorrect; member
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | tegra20-paz00.dts | 398 * name is incorrect; perhaps copied
399 * from an incorrect NVIDIA reference.
|
| /linux-4.1.27/arch/m68k/math-emu/ |
| D | fp_entry.S | 112 | instruction decoding, otherwise the stack pointer is incorrect
|
| /linux-4.1.27/arch/arm64/ |
| D | Kconfig | 396 bool "Cortex-A53: 845719: a load might read incorrect data"
406 might return incorrect data.
417 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
423 a subsequent memory access to use an incorrect address on Cortex-A53
|
| /linux-4.1.27/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 136 This bug can cause incorrect code execution under certain
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.arcmsr | 40 ** 1.20.00.11 9/29/2005 Erich Chen by comment of Arjan van de Ven fix incorrect msleep…
|
| D | in2000.txt | 26 Fixed a bug that caused incorrect SCSI status bytes to be
|
| D | ChangeLog.lpfc | 273 of ulpPU and fcpi_parm to avoid incorrect read check of Write IO
274 and incorrect read length.
|
| /linux-4.1.27/Documentation/x86/i386/ |
| D | IO-APIC.txt | 102 'incorrect' pirq line will cause the booting process to hang, or a device
|
| /linux-4.1.27/Documentation/early-userspace/ |
| D | buffer-format.txt | 77 clearly incorrect (a cyclic redundancy check is a different and
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | overview.txt | 59 and to discourage meaningless and incorrect casts between the two.
|
| /linux-4.1.27/Documentation/i2c/ |
| D | fault-codes | 54 on these as the only way to detect incorrect data transfers.
|
| /linux-4.1.27/Documentation/networking/ |
| D | skfp.txt | 190 - Interrupt routing on SMP machines could be incorrect
|
| D | cxgb.txt | 239 2. After running insmod, the driver is loaded and the incorrect network
253 network card, your new interface will have incorrect IP address and
|
| D | e100.txt | 79 NOTE: setting the speed/duplex to incorrect values will cause the link to
|
| D | 3c509.txt | 152 likely have an unterminated network or the incorrect media transceiver selected.
|
| D | arcnet-hardware.txt | 723 off | defective board or | incorrect memory or
950 off | defective board or | incorrect memory or
|
| D | filter.txt | 1220 accesses the memory with incorrect alignment:
|
| /linux-4.1.27/Documentation/block/ |
| D | biovecs.txt | 95 * Almost all usage of bi_idx is now incorrect and has been removed; instead,
|
| /linux-4.1.27/Documentation/ |
| D | svga.txt | 201 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
|
| D | kobject.txt | 30 up and incorrect, and your code will be buggy. So do not do this.
146 incorrect and needs to be fixed.
|
| D | kprobes.txt | 460 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
|
| D | intel_txt.txt | 97 incorrect), it will directly launch the kernel with no changes
|
| D | robust-futexes.txt | 95 is empty. If the thread/process crashed or terminated in some incorrect
|
| D | DMA-API-HOWTO.txt | 559 from panics to silent data corruption. A couple of examples of incorrect ways
|
| D | kernel-parameters.txt | 920 send no or incorrect EDID data sets. This parameter
1921 significantly divergent settings. An incorrect value
|
| D | memory-barriers.txt | 958 Apparently incorrect ---> | | B->7 |------>| |
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 535 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).
|
| D | README | 347 coherency checks (i.e. incorrect attribute cache for a short
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | uvcvideo.txt | 224 The specified buffer size is incorrect (too big or too small).
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ext3.txt | 168 mode - metadata journaling. A crash+recovery can cause incorrect data to
|
| D | path-lookup.txt | 115 lookup of the old list veering off into the new (incorrect) list and missing
|
| D | ext4.txt | 400 mode - metadata journaling. A crash+recovery can cause incorrect data to
|
| D | proc.txt | 92 complaining about how you screwed up your system because of incorrect
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 176 serve incorrect data.
307 any file of an incorrect type (such as a FIFO file or a device file).
|
| /linux-4.1.27/Documentation/s390/ |
| D | cds.txt | 250 CCW_FLAG_SLI - suppress incorrect length
311 SCHN_STAT_INCORR_LEN - incorrect length
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig.debug | 95 in order to catch accidental (and incorrect) writes to such const
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1020 bool "ARM errata: FSR write bit incorrect on a SWP to read-only memory"
1047 executing the new code sequence in the incorrect ARM or Thumb state.
1109 bool "ARM errata: LoUIS bit field in CLIDR register is incorrect"
1225 bool "ARM errata: incorrect instructions may be executed from loop buffer"
1230 loop buffer may deliver incorrect instructions. This
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | boot-options.txt | 80 problems with incorrect timer initialization on some boards.
|
| /linux-4.1.27/arch/m68k/ |
| D | Kconfig.cpu | 315 mantissa and round slightly incorrect, what is more than enough
|
| /linux-4.1.27/Documentation/ide/ |
| D | ChangeLog.ide-tape.1995-2002 | 135 * MTTELL was sometimes returning incorrect results.
|
| /linux-4.1.27/Documentation/fb/ |
| D | framebuffer.txt | 152 work 100% with XF68_FBDev: the reported clock values are always incorrect.
|
| /linux-4.1.27/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 963 # 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 #
|
| D | fpsp.S | 964 # 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.1.27/Documentation/ABI/testing/ |
| D | sysfs-bus-pci | 292 source. If that is missing or incorrect, this file can be
|
| /linux-4.1.27/drivers/mtd/nand/ |
| D | Kconfig | 190 incorrect ECC generation, and if using these, the default of
|
| /linux-4.1.27/scripts/genksyms/ |
| D | parse.tab.c_shipped | 2180 incorrect destructor might then be invoked immediately. In the
2182 to an incorrect destructor call or verbose syntax error message
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 2069 incorrect destructor might then be invoked immediately. In the
2071 to an incorrect destructor call or verbose syntax error message
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 2082 incorrect destructor might then be invoked immediately. In the
2084 to an incorrect destructor call or verbose syntax error message
|
| /linux-4.1.27/Documentation/trace/ |
| D | ring-buffer-design.txt | 943 the reader from seeing the incorrect head page.
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 4.Coding | 363 out. Anything which might tempt a code janitor to make an incorrect
|
| /linux-4.1.27/Documentation/arm64/ |
| D | arm-acpi.txt | 140 the ACPI signature "RSD PTR "). If this pointer is incorrect and acpi=force
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 955 bool "Lock debugging: detect incorrect freeing of live locks"
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 901 "line" size here which is incorrect. The kernel will prefer the cache
|