Home
last modified time | relevance | path

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

12345678910>>...15

/Linux-v6.1/tools/testing/selftests/kvm/x86_64/
Dvmx_dirty_log_test.c135 TEST_ASSERT(test_bit(0, bmap), "Page 0 incorrectly reported clean\n"); in main()
138 TEST_ASSERT(!test_bit(0, bmap), "Page 0 incorrectly reported dirty\n"); in main()
142 TEST_ASSERT(!test_bit(1, bmap), "Page 1 incorrectly reported dirty\n"); in main()
144 TEST_ASSERT(!test_bit(2, bmap), "Page 2 incorrectly reported dirty\n"); in main()
/Linux-v6.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-v6.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-v6.1/Documentation/devicetree/bindings/dma/
Dqcom_hidma_mgmt.txt24 writing into destination memory. Setting this value incorrectly can
29 reading the source memory. Setting this value incorrectly can starve
/Linux-v6.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-v6.1/arch/x86/power/
DMakefile7 # Clang may incorrectly inline functions with stack protector enabled into
/Linux-v6.1/arch/mips/include/asm/vdso/
Dprocessor.h14 * hardware (incorrectly) doesn't ensure that writes will eventually occur.
/Linux-v6.1/arch/arm64/boot/dts/qcom/
Dsc7180-trogdor-lazor-r0.dts21 * Lane 0 was incorrectly mapped on the cable, but we've now decided
/Linux-v6.1/Documentation/arm64/
Dtagged-address-abi.rst55 incorrectly accept valid tagged pointers for the ``brk()``,
65 incorrectly accept valid tagged pointers for this system call.
/Linux-v6.1/arch/x86/include/uapi/asm/
Dsembuf.h15 * x86_64 and x32 incorrectly added padding here, so the structures
/Linux-v6.1/Documentation/userspace-api/media/v4l/
Dvidioc-log-status.rst34 dealing with problems like no sound, no video and incorrectly tuned
/Linux-v6.1/Documentation/devicetree/bindings/net/wireless/
Dieee80211.yaml30 different 5 GHz subbands. Using them incorrectly could not work or
/Linux-v6.1/tools/testing/selftests/drivers/net/ocelot/
Dpsfp.sh220 echo "Packets incorrectly dropped:"
242 echo "Packets incorrectly received:"
/Linux-v6.1/drivers/spi/
Dspi-pl022.c1622 "interface is configured incorrectly\n"); in verify_controller_parameters()
1635 "hierarchy is configured incorrectly\n"); in verify_controller_parameters()
1642 "Communication mode is configured incorrectly\n"); in verify_controller_parameters()
1654 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1661 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1667 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1679 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1686 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1692 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1699 "CTRL LEN is configured incorrectly\n"); in verify_controller_parameters()
[all …]
/Linux-v6.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-v6.1/Documentation/admin-guide/
Dedid.rst17 - The graphics board incorrectly forwards EDID data to the driver.
/Linux-v6.1/Documentation/x86/
Dpti.rst173 incorrectly mapping the IRQ handler entry code.
176 normal interrupts. Also caused by incorrectly mapping NMI
/Linux-v6.1/fs/squashfs/
Dfragment.c72 * incorrectly larger than the next table start in squashfs_read_fragment_index_table()
/Linux-v6.1/Documentation/hwmon/
Dthmc50.rst64 In case the BIOS is broken and the mode is set incorrectly, you can force
/Linux-v6.1/tools/testing/selftests/ftrace/
DREADME61 or the test was set up incorrectly
/Linux-v6.1/tools/testing/selftests/gpio/
Dgpio-sim.sh330 test "$?" = "1" || fail "pull set incorrectly"
333 test "$?" = "0" || fail "pull set incorrectly"
/Linux-v6.1/drivers/gpu/drm/i915/selftests/
Di915_sw_fence.c194 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-v6.1/crypto/asymmetric_keys/
Dpkcs7.asn156 CertificateList ::= SEQUENCE OF Certificate -- This may be defined incorrectly
/Linux-v6.1/drivers/bus/
Dsimple-pm-bus.c37 * the most specific match because we don't want to incorrectly bind to in simple_pm_bus_probe()

12345678910>>...15