Home
last modified time | relevance | path

Searched full:worked (Results 1 – 25 of 269) sorted by relevance

1234567891011

/linux/arch/x86/kernel/
H A Dsmp.c65 * 2AP. worked around in hardware
68 * 4AP. worked around in hardware
94 * 6AP. not affected - worked around in hardware
95 * 7AP. not affected - worked around in hardware
96 * 8AP. worked around in hardware - we get explicit CS errors if not
100 * 10AP. not affected - worked around in hardware
104 * 12AP. not affected - worked around in hardware
105 * 13AP. not affected - worked around in hardware
107 * 15AP. not affected - worked around in hardware
108 * 16AP. not affected - worked around in hardware
[all …]
/linux/Documentation/scsi/
H A Dsym53c500_cs.rst15 not have worked anyway. The USE_DMA code is likewise gone. Many thanks
26 version of this driver, and I guess it worked for those users. It worked
/linux/tools/testing/selftests/net/forwarding/
H A Dbridge_locked_port.sh105 check_fail $? "Ping worked after locking port, but before adding FDB entry"
135 check_fail $? "Ping through vlan worked after locking port, but before adding FDB entry"
164 check_fail $? "Ping6 worked after locking port, but before adding FDB entry"
190 check_fail $? "Ping worked on a locked port without an FDB entry"
198 check_fail $? "Ping worked on MAB enabled port without an FDB entry"
345 check_fail $? "Ping worked without redirection"
H A Dbridge_port_isolation.sh106 check_fail $? "Ping worked when it should not have"
119 check_fail $? "Ping6 worked when it should not have"
/linux/drivers/gpio/
H A Dgpio-zynqmp-modepin.c23 * @chip: gpio_chip instance to be worked on
51 * @chip: gpio_chip instance to be worked on
84 * @chip: gpio_chip instance to be worked on
96 * @chip: gpio_chip instance to be worked on
H A Dgpio-zynq.c218 * @chip: gpio_chip instance to be worked on
260 * @chip: gpio_chip instance to be worked on
297 * @chip: gpio_chip instance to be worked on
334 * @chip: gpio_chip instance to be worked on
373 * @chip: gpio_chip instance to be worked on
/linux/tools/testing/selftests/x86/
H A Dioperm.c75 printf("[OK]\toutb to 0x%02hx worked\n", port); in expect_ok()
81 printf("[FAIL]\toutb to 0x%02hx worked\n", port); in expect_gp()
161 printf("\tVerify that unsharing the bitmap worked\n"); in main()
176 printf("[OK]\tit worked\n"); in main()
H A Diopl.c75 printf("[OK]\toutb to 0x%02hx worked\n", port); in expect_ok_outb()
81 printf("[FAIL]\toutb to 0x%02hx worked\n", port); in expect_gp_outb()
144 printf("[FAIL]\tSTI worked\n"); in expect_gp_sti()
164 printf("[FAIL]\tCLI worked\n"); in test_cli()
H A Dsyscall_nt.c46 printf("[OK]\tThe syscall worked and flags are still set\n"); in do_it()
48 …printf("[FAIL]\tThe syscall worked but flags were cleared (flags = 0x%lx but expected 0x%lx set)\n… in do_it()
/linux/tools/testing/selftests/kvm/aarch64/
H A Dvcpu_width_config.c115 "Configuring mixed-width vCPUs worked unexpectedly"); in main()
118 "Configuring mixed-width vCPUs worked unexpectedly"); in main()
/linux/Documentation/filesystems/smb/
H A Dksmbd.rst41 ownership of receiving/parsing of SMB commands. Each received command is worked
42 in parallel i.e., there can be multiple client commands which are worked in
96 Integration with Samba tools is being worked on
/linux/arch/arm/mach-sa1100/
H A Djornada720_ssp.c141 /* worked fine, lets not bother with anything else */ in jornada_ssp_probe()
163 /* seems like it worked, just feed it with TxDummy to get rid of data */ in jornada_ssp_probe()
/linux/tools/sched_ext/include/bpf-compat/gnu/
H A Dstubs.h9 * The problem is worked around by making this file available in the include
/linux/tools/testing/selftests/sched_ext/
H A Denq_select_cpu_fails.bpf.c27 * Improving these semantics is actively being worked on. in BPF_STRUCT_OPS()
/linux/tools/testing/selftests/ftrace/test.d/ftrace/
H A Dfunc_profiler.tc12 # broke the way filtering of the function tracer worked.
/linux/Documentation/devicetree/bindings/spi/
H A Dbrcm,bcm63xx-spi.yaml18 transaction to some SPI devices prematurely. The issue can be worked around by
/linux/drivers/staging/
H A DKconfig20 worked on, and who to contact.
/linux/net/sctp/
H A Dinqueue.c41 /* Properly release the chunk which is being worked on. */
60 /* If there is a packet which is currently being worked on, in sctp_inq_free()
/linux/Documentation/admin-guide/media/
H A Dcx88.rst48 cx88-cards.c. If that worked, mail me your changes as unified
/linux/arch/x86/entry/vdso/vdso32/
H A Dsystem_call.S30 * it working approximately as well as it ever worked.
/linux/Documentation/core-api/irq/
H A Dirqflags-tracing.rst17 for rwsems is worked around)
/linux/Documentation/driver-api/usb/
H A Derror-codes.rst71 some problem that could not be worked around.
173 be worked around, such as a physical
/linux/tools/testing/selftests/mm/
H A Dgup_longterm.c186 ksft_test_result(should_work, "Should have worked\n"); in do_test()
226 ksft_test_result(should_work, "Should have worked\n"); in do_test()
/linux/Documentation/process/
H A Dhandling-regressions.rst650 worked for him/her.
652 Maybe it worked *because* the user had taken the bug into account,
653 maybe it worked because the user didn't notice - again, it doesn't
654 matter. It worked for the user.
659 It's basically saying "I took something that worked, and I broke it,
777 "should never have worked in the first place". It's about whether
/linux/arch/x86/include/asm/
H A Dpage_64.h78 * bad things happen. This is worked around in the same way as the

1234567891011