Home
last modified time | relevance | path

Searched full:incorrectly (Results 1 – 25 of 426) sorted by relevance

12345678910>>...18

/linux-6.12.1/arch/m68k/fpsp040/
Dx_operr.S16 | 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.12.1/tools/testing/selftests/kvm/x86_64/
Dvmx_dirty_log_test.c148 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-6.12.1/tools/testing/selftests/sched_ext/
Denq_last_no_enq_fails.c35 SCX_ERR("Incorrectly failed at attaching scheduler"); in run()
39 SCX_ERR("Incorrectly stayed loaded"); in run()
/linux-6.12.1/arch/mips/include/asm/
Dcompiler.h18 * incorrectly reordered into earlier delay slots if the unreachable statement
20 * seemingly random behaviour, such as invalid memory accesses from incorrectly
/linux-6.12.1/tools/testing/selftests/net/forwarding/
Dtc_chains.sh139 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.12.1/arch/x86/power/
DMakefile7 # Clang may incorrectly inline functions with stack protector enabled into
/linux-6.12.1/drivers/media/pci/intel/ipu6/
DKconfig8 # This driver incorrectly tries to override the dma_ops. It should
/linux-6.12.1/arch/mips/include/asm/vdso/
Dprocessor.h14 * hardware (incorrectly) doesn't ensure that writes will eventually occur.
/linux-6.12.1/drivers/spi/
Dspi-pl022.c1375 "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.12.1/Documentation/arch/arm64/
Dtagged-address-abi.rst55 incorrectly accept valid tagged pointers for the ``brk()``,
65 incorrectly accept valid tagged pointers for this system call.
/linux-6.12.1/arch/x86/include/uapi/asm/
Dsembuf.h15 * x86_64 and x32 incorrectly added padding here, so the structures
/linux-6.12.1/Documentation/admin-guide/
Dedid.rst17 - The graphics board incorrectly forwards EDID data to the driver.
/linux-6.12.1/Documentation/devicetree/bindings/net/wireless/
Dieee80211.yaml29 different 5 GHz subbands. Using them incorrectly could not work or
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dvidioc-log-status.rst34 dealing with problems like no sound, no video and incorrectly tuned
/linux-6.12.1/tools/testing/selftests/drivers/net/ocelot/
Dpsfp.sh220 echo "Packets incorrectly dropped:"
242 echo "Packets incorrectly received:"
/linux-6.12.1/arch/riscv/include/asm/
Dmembarrier.h42 * is zero, switch_mm() may incorrectly skip the sync-core. in membarrier_arch_switch_mm()
/linux-6.12.1/include/linux/
Dpacking.h41 * Return: 0 on success, EINVAL or ERANGE if called incorrectly. Assuming
Dsmsc911x.h43 * "last resort" in the case of big endian mode on boards with incorrectly
/linux-6.12.1/drivers/md/dm-vdo/
Dstatus-codes.h49 /* a lock is held incorrectly */
/linux-6.12.1/Documentation/arch/x86/
Dpti.rst171 incorrectly mapping the IRQ handler entry code.
174 normal interrupts. Also caused by incorrectly mapping NMI
/linux-6.12.1/fs/squashfs/
Dfragment.c72 * incorrectly larger than the next table start in squashfs_read_fragment_index_table()
/linux-6.12.1/Documentation/hwmon/
Dthmc50.rst64 In case the BIOS is broken and the mode is set incorrectly, you can force
/linux-6.12.1/drivers/hid/
Dhid-glorious.c25 * Glorious Model I incorrectly specifes the Usage Minimum for its
/linux-6.12.1/tools/testing/selftests/power_supply/
Dtest_power_supply_properties.sh91 # 1.8V-60V to catch drivers reporting incorrectly scaled values. E.g. a
/linux-6.12.1/tools/testing/selftests/ftrace/
DREADME61 or the test was set up incorrectly

12345678910>>...18