Searched full:incorrectly (Results 1 – 25 of 328) sorted by relevance
12345678910>>...14
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/tools/testing/selftests/kvm/x86_64/ |
| D | vmx_dirty_log_test.c | 138 TEST_ASSERT(test_bit(0, bmap), "Page 0 incorrectly reported clean\n"); in main()
141 TEST_ASSERT(!test_bit(0, bmap), "Page 0 incorrectly reported dirty\n"); in main()
145 TEST_ASSERT(!test_bit(1, bmap), "Page 1 incorrectly reported dirty\n"); in main()
147 TEST_ASSERT(!test_bit(2, bmap), "Page 2 incorrectly reported dirty\n"); in main()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | tc_chains.sh | 139 check_fail $? "Incorrectly succeded to insert filter which does not template"
147 check_fail $? "Incorrectly succeded to insert filter which does not template"
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/qcom/ |
| D | sc7180-trogdor-lazor-r0.dts | 19 * Lane 0 was incorrectly mapped on the cable, but we've now decided
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/vdso/ |
| D | processor.h | 14 * hardware (incorrectly) doesn't ensure that writes will eventually occur.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/wireless/ |
| D | ieee80211.txt | 13 incorrectly could not work or decrease performance noticeably.
|
| /kernel/linux/linux-5.10/arch/x86/include/uapi/asm/ |
| D | sembuf.h | 15 * x86_64 and x32 incorrectly added padding here, so the structures
|
| /kernel/linux/linux-5.10/Documentation/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.
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-log-status.rst | 34 dealing with problems like no sound, no video and incorrectly tuned
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/spi/ |
| D | spi-pl022.c | 1629 "interface is configured incorrectly\n"); in verify_controller_parameters()
1642 "hierarchy is configured incorrectly\n"); in verify_controller_parameters()
1649 "Communication mode is configured incorrectly\n"); in verify_controller_parameters()
1661 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1668 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1674 "RX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1686 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1693 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1699 "TX FIFO Trigger Level is configured incorrectly\n"); in verify_controller_parameters()
1706 "CTRL LEN is configured incorrectly\n"); in verify_controller_parameters()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | edid.rst | 17 - The graphics board incorrectly forwards EDID data to the driver.
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | pti.rst | 173 incorrectly mapping the IRQ handler entry code.
176 normal interrupts. Also caused by incorrectly mapping NMI
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | thmc50.rst | 64 In case the BIOS is broken and the mode is set incorrectly, you can force
|
| /kernel/linux/linux-5.10/tools/testing/selftests/ftrace/ |
| D | README | 61 or the test was set up incorrectly
|
| /kernel/linux/linux-5.10/tools/testing/selftests/powerpc/include/ |
| D | basic_asm.h | 56 * preprocessed incorrectly, hence r0.
|
| /kernel/linux/linux-5.10/fs/squashfs/ |
| D | fragment.c | 72 * incorrectly larger than the next table start in squashfs_read_fragment_index_table()
|
| /kernel/linux/linux-5.10/drivers/ide/ |
| D | ide-pio-blacklist.c | 3 * PIO blacklist. Some drives incorrectly report their maximal PIO mode,
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-ocores.txt | 28 drivers, but it was incorrectly used to specify i2c controller input clock
|
| /kernel/linux/linux-5.10/crypto/asymmetric_keys/ |
| D | pkcs7.asn1 | 56 CertificateList ::= SEQUENCE OF Certificate -- This may be defined incorrectly
|
| /kernel/linux/linux-5.10/drivers/media/rc/img-ir/ |
| D | img-ir-rc6.c | 19 * raw data is shifted incorrectly. in img_ir_rc6_scancode()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/x86/ |
| D | check_initial_reg_state.c | 59 printf("[FAIL]\tTest was built incorrectly\n"); in main()
|
12345678910>>...14