Searched full:incorrectly (Results 1 – 25 of 397) sorted by relevance
12345678910>>...16
| /linux-6.8/tools/testing/selftests/kvm/x86_64/ |
| D | vmx_dirty_log_test.c | 131 TEST_ASSERT(test_bit(0, bmap), "Page 0 incorrectly reported clean"); in main()
134 TEST_ASSERT(!test_bit(0, bmap), "Page 0 incorrectly reported dirty"); in main()
138 TEST_ASSERT(!test_bit(1, bmap), "Page 1 incorrectly reported dirty"); in main()
140 TEST_ASSERT(!test_bit(2, bmap), "Page 2 incorrectly reported dirty"); in main()
|
| /linux-6.8/arch/m68k/fpsp040/ |
| 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-6.8/arch/mips/include/asm/ |
| 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-6.8/Documentation/devicetree/bindings/dma/ |
| D | qcom_hidma_mgmt.txt | 24 writing into destination memory. Setting this value incorrectly can
29 reading the source memory. Setting this value incorrectly can starve
|
| /linux-6.8/drivers/gpu/drm/ci/xfails/ |
| D | msm-sc7180-skips.txt | 4 # Test incorrectly assumes that CTM support implies gamma/degamma
|
| /linux-6.8/tools/testing/selftests/net/forwarding/ |
| 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-6.8/arch/x86/power/ |
| D | Makefile | 7 # Clang may incorrectly inline functions with stack protector enabled into
|
| /linux-6.8/arch/mips/include/asm/vdso/ |
| D | processor.h | 14 * hardware (incorrectly) doesn't ensure that writes will eventually occur.
|
| /linux-6.8/drivers/spi/ |
| D | spi-pl022.c | 1375 "interface is configured incorrectly\n"); in verify_controller_parameters()
1388 "hierarchy is configured incorrectly\n"); in verify_controller_parameters()
1395 "Communication mode is configured incorrectly\n"); in verify_controller_parameters()
1407 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1414 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1420 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1432 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1439 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1445 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1452 "CTRL LEN is configured incorrectly\n"); in verify_controller_parameters()
[all …]
|
| /linux-6.8/Documentation/arch/arm64/ |
| 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-6.8/arch/x86/include/uapi/asm/ |
| D | sembuf.h | 15 * x86_64 and x32 incorrectly added padding here, so the structures
|
| /linux-6.8/Documentation/devicetree/bindings/net/wireless/ |
| D | ieee80211.yaml | 29 different 5 GHz subbands. Using them incorrectly could not work or
|
| /linux-6.8/Documentation/userspace-api/media/v4l/ |
| D | vidioc-log-status.rst | 34 dealing with problems like no sound, no video and incorrectly tuned
|
| /linux-6.8/tools/testing/selftests/drivers/net/ocelot/ |
| D | psfp.sh | 220 echo "Packets incorrectly dropped:"
242 echo "Packets incorrectly received:"
|
| /linux-6.8/include/linux/ |
| D | packing.h | 41 * Return: 0 on success, EINVAL or ERANGE if called incorrectly. Assuming
|
| D | smsc911x.h | 43 * "last resort" in the case of big endian mode on boards with incorrectly
|
| /linux-6.8/Documentation/arch/x86/ |
| D | pti.rst | 171 incorrectly mapping the IRQ handler entry code.
174 normal interrupts. Also caused by incorrectly mapping NMI
|
| /linux-6.8/Documentation/admin-guide/ |
| D | edid.rst | 17 - The graphics board incorrectly forwards EDID data to the driver.
|
| /linux-6.8/drivers/hid/ |
| D | hid-glorious.c | 25 * Glorious Model I incorrectly specifes the Usage Minimum for its
|
| /linux-6.8/fs/squashfs/ |
| D | fragment.c | 72 * incorrectly larger than the next table start in squashfs_read_fragment_index_table()
|
| /linux-6.8/tools/testing/selftests/ftrace/ |
| D | README | 61 or the test was set up incorrectly
|
| /linux-6.8/Documentation/hwmon/ |
| D | thmc50.rst | 64 In case the BIOS is broken and the mode is set incorrectly, you can force
|
| /linux-6.8/tools/testing/selftests/gpio/ |
| D | gpio-sim.sh | 330 test "$?" = "1" || fail "pull set incorrectly"
333 test "$?" = "0" || fail "pull set incorrectly"
|
| /linux-6.8/drivers/gpu/drm/i915/selftests/ |
| 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-6.8/tools/testing/selftests/x86/ |
| D | check_initial_reg_state.c | 59 printf("[FAIL]\tTest was built incorrectly\n"); in main()
|
12345678910>>...16