| /linux/arch/m68k/fpsp040/ |
| H A D | x_operr.S | 16 | There are three cases in which operr is incorrectly signaled on the
123 | CHECK FOR INCORRECTLY GENERATED OPERR EXCEPTION HERE
170 | CHECK FOR INCORRECTLY GENERATED OPERR EXCEPTION HERE
197 | CHECK FOR INCORRECTLY GENERATED OPERR EXCEPTION HERE
223 | the operr and aiop bits, and clears inex and ainex, incorrectly
290 cmpiw #0xc000,FPTEMP_EX(%a6) |check if incorrectly signalled
292 cmpiw #0xbfff,FPTEMP_EX(%a6) |check if incorrectly signalled
|
| /linux/tools/testing/selftests/kvm/x86_64/ |
| H A D | vmx_dirty_log_test.c | 148 TEST_ASSERT(test_bit(0, bmap), "Page 0 incorrectly reported clean"); in test_vmx_dirty_log()
151 TEST_ASSERT(!test_bit(0, bmap), "Page 0 incorrectly reported dirty"); in test_vmx_dirty_log()
155 TEST_ASSERT(!test_bit(1, bmap), "Page 1 incorrectly reported dirty"); in test_vmx_dirty_log()
157 TEST_ASSERT(!test_bit(2, bmap), "Page 2 incorrectly reported dirty"); in test_vmx_dirty_log()
|
| /linux/tools/testing/selftests/sched_ext/ |
| H A D | enq_last_no_enq_fails.c | 35 SCX_ERR("Incorrectly failed at attaching scheduler"); in run()
39 SCX_ERR("Incorrectly stayed loaded"); in run()
|
| /linux/arch/mips/include/asm/ |
| H A D | compiler.h | 18 * incorrectly reordered into earlier delay slots if the unreachable statement
20 * seemingly random behaviour, such as invalid memory accesses from incorrectly
|
| /linux/tools/testing/selftests/net/forwarding/ |
| H A D | tc_chains.sh | 139 check_fail $? "Incorrectly succeeded to insert filter which does not template"
147 check_fail $? "Incorrectly succeeded to insert filter which does not template"
|
| /linux/arch/x86/power/ |
| H A D | Makefile | 7 # Clang may incorrectly inline functions with stack protector enabled into
|
| /linux/Documentation/arch/arm64/ |
| H A D | tagged-address-abi.rst | 55 incorrectly accept valid tagged pointers for the ``brk()``,
65 incorrectly accept valid tagged pointers for this system call.
|
| /linux/arch/mips/include/asm/vdso/ |
| H A D | processor.h | 14 * hardware (incorrectly) doesn't ensure that writes will eventually occur.
|
| /linux/arch/x86/include/uapi/asm/ |
| H A D | sembuf.h | 15 * x86_64 and x32 incorrectly added padding here, so the structures
|
| /linux/Documentation/admin-guide/ |
| H A D | edid.rst | 17 - The graphics board incorrectly forwards EDID data to the driver.
|
| /linux/tools/testing/selftests/drivers/net/ocelot/ |
| H A D | psfp.sh | 220 echo "Packets incorrectly dropped:"
242 echo "Packets incorrectly received:"
|
| /linux/Documentation/devicetree/bindings/net/wireless/ |
| H A D | ieee80211.yaml | 29 different 5 GHz subbands. Using them incorrectly could not work or
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-log-status.rst | 34 dealing with problems like no sound, no video and incorrectly tuned
|
| /linux/arch/riscv/include/asm/ |
| H A D | membarrier.h | 42 * is zero, switch_mm() may incorrectly skip the sync-core. in membarrier_arch_switch_mm()
|
| /linux/Documentation/arch/x86/ |
| H A D | pti.rst | 171 incorrectly mapping the IRQ handler entry code.
174 normal interrupts. Also caused by incorrectly mapping NMI
|
| /linux/drivers/md/dm-vdo/ |
| H A D | status-codes.h | 49 /* a lock is held incorrectly */
|
| /linux/include/linux/ |
| H A D | smsc911x.h | 43 * "last resort" in the case of big endian mode on boards with incorrectly
|
| /linux/drivers/gpu/drm/i915/selftests/ |
| H A D | i915_sw_fence.c | 194 pr_err("Incorrectly reported fence A was complete before await\n"); in test_AB()
249 pr_err("Incorrectly reported fence B was complete before await\n"); in test_ABC()
257 pr_err("Incorrectly reported fence C was complete before await\n"); in test_ABC()
|
| /linux/tools/testing/selftests/gpio/ |
| H A D | gpio-sim.sh | 330 test "$?" = "1" || fail "pull set incorrectly"
333 test "$?" = "0" || fail "pull set incorrectly"
|
| /linux/fs/squashfs/ |
| H A D | fragment.c | 72 * incorrectly larger than the next table start in squashfs_read_fragment_index_table()
|
| /linux/Documentation/hwmon/ |
| H A D | thmc50.rst | 64 In case the BIOS is broken and the mode is set incorrectly, you can force
|
| /linux/tools/testing/selftests/ftrace/ |
| H A D | README | 61 or the test was set up incorrectly
|
| /linux/tools/testing/selftests/power_supply/ |
| H A D | test_power_supply_properties.sh | 91 # 1.8V-60V to catch drivers reporting incorrectly scaled values. E.g. a
|
| /linux/drivers/hid/ |
| H A D | hid-glorious.c | 25 * Glorious Model I incorrectly specifes the Usage Minimum for its
|
| /linux/drivers/gpio/ |
| H A D | gpiolib-of.c | 53 * * %-EINVAL for an incorrectly formed "gpios" property, or
86 * * %-EINVAL for an incorrectly formed "gpios" property, or
190 * Himax LCD controllers used incorrectly named in of_gpio_try_fixup_polarity()
210 * have been widely used for a long time incorrectly describe in of_gpio_try_fixup_polarity()
218 * DTS for Nokia N900 incorrectly specified "active high" in of_gpio_try_fixup_polarity()
|