| /linux/tools/testing/selftests/cpu-hotplug/ |
| H A D | cpu-on-off-test.sh | 105 echo $FUNCNAME $cpu: unexpected fail >&2
108 echo $FUNCNAME $cpu: unexpected offline >&2
118 echo $FUNCNAME $cpu: unexpected success >&2
121 echo $FUNCNAME $cpu: unexpected online >&2
131 echo $FUNCNAME $cpu: unexpected fail >&2
134 echo $FUNCNAME $cpu: unexpected offline >&2
144 echo $FUNCNAME $cpu: unexpected success >&2
147 echo $FUNCNAME $cpu: unexpected offline >&2
|
| /linux/tools/testing/selftests/memory-hotplug/ |
| H A D | mem-on-off-test.sh | 86 echo $FUNCNAME $memory: unexpected fail >&2
89 echo $FUNCNAME $memory: unexpected offline >&2
100 echo $FUNCNAME $memory: unexpected success >&2
103 echo $FUNCNAME $memory: unexpected online >&2
114 echo $FUNCNAME $memory: unexpected fail >&2
117 echo $FUNCNAME $memory: unexpected offline >&2
128 echo $FUNCNAME $memory: unexpected success >&2
131 echo $FUNCNAME $memory: unexpected offline >&2
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | local_storage_rcu_tasks_trace_bench.c | 19 long unexpected; variable
56 __sync_add_and_fetch(&unexpected, 1); in postgp()
|
| /linux/Documentation/infiniband/ |
| H A D | tag_matching.rst | 24 this is an expected message, otherwise it is called an unexpected message.
45 unexpected message list. The application posts receive buffers through calls
52 placed in the unexpected message list. Otherwise the match is processed,
58 the software unexpected message list for a matching receive. If a match is
68 hardware, as the matching unexpected message is being passed from the hardware
|
| /linux/drivers/staging/gpib/ni_usb/ |
| H A D | ni_usb_gpib.c | 371 int unexpected = 0; in ni_usb_parse_register_read_block() local
379 unexpected = 1; in ni_usb_parse_register_read_block()
388 unexpected = 1; in ni_usb_parse_register_read_block()
393 unexpected = 1; in ni_usb_parse_register_read_block()
397 pr_err("unexpected data: raw_data[%i]=0x%x, expected 0\n", in ni_usb_parse_register_read_block()
399 unexpected = 1; in ni_usb_parse_register_read_block()
402 if (unexpected) in ni_usb_parse_register_read_block()
415 pr_err("received unexpected termination block\n"); in ni_usb_parse_termination_block()
435 int unexpected = 0; in parse_board_ibrd_readback() local
443 pr_err("unexpected dat in parse_board_ibrd_readback()
1990 int unexpected = 0; ni_usb_hs_wait_for_ready() local
[all...] |
| /linux/fs/overlayfs/ |
| H A D | Kconfig | 27 feature will have unexpected results.
61 that doesn't support this feature will have unexpected results.
86 that doesn't support this feature will have unexpected results.
125 that doesn't support this feature will have unexpected results.
|
| /linux/kernel/trace/rv/monitors/rtapp/ |
| H A D | Kconfig | 7 application that may cause unexpected latency.
|
| /linux/Documentation/tools/rtla/ |
| H A D | rtla.rst | 19 precise information about the properties and root causes of unexpected
|
| /linux/tools/tracing/rtla/ |
| H A D | README.txt | 6 about the properties and root causes of unexpected results.
|
| /linux/tools/testing/selftests/bpf/benchs/ |
| H A D | bench_local_storage_rcu_tasks_trace.c | 209 if (ctx.skel->bss->unexpected) { in report_progress()
|
| /linux/Documentation/arch/arm64/ |
| H A D | legacy_instructions.rst | 68 be unexpected results in the application.
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | error-codes.rst | 75 applications should abort on unexpected errors, or otherwise
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | floppy.rst | 166 Print a warning message when an unexpected interrupt is received.
170 Don't print a message when an unexpected interrupt is received. This
172 to be an interaction between video and floppy. The unexpected
|
| /linux/Documentation/trace/rv/ |
| H A D | monitor_rtapp.rst | 12 unexpected latency and fail to meet their time requirements. Often, these flaws
26 reasons for unexpected latency with real-time applications. It is a container of
|
| H A D | runtime-verification.rst | 19 *online* verification of a system, enabling the *reaction* for unexpected
55 react to an unexpected event. The forms of reaction can vary from logging the
|
| /linux/drivers/soc/mediatek/ |
| H A D | Kconfig | 25 unexpected transaction.
|
| /linux/tools/testing/selftests/futex/ |
| H A D | README | 44 ERROR: Description of unexpected error
|
| /linux/scripts/ |
| H A D | spelling.txt | 1694 unexecpted||unexpected
1695 unexepected||unexpected
1696 unexpcted||unexpected
1697 unexpectd||unexpected
1698 unexpeted||unexpected
1699 unexpexted||unexpected
|
| /linux/drivers/firmware/arm_scmi/ |
| H A D | Kconfig | 45 order to avoid unexpected interactions with the SCMI Raw message
|
| /linux/Documentation/admin-guide/ |
| H A D | tainted-kernels.rst | 90 5 _/B 32 bad page referenced or some unexpected page flags
152 unexpected page flags. This indicates a hardware problem or a kernel bug;
|
| H A D | syscall-user-dispatch.rst | 41 ABI is completely unexpected to Linux. Syscall User Dispatch, therefore
|
| /linux/Documentation/networking/devlink/ |
| H A D | mlx5.rst | 277 number of packets generated by the VNIC experiencing unexpected steering
280 number of packets handled by the VNIC experiencing unexpected steering
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | README.rst | 319 libbpf: ELF relo #0 in section #6 has unexpected type 2 in .../bpf_tcp_nogpl.bpf.o
337 test_xdpwall:FAIL:Does LLVM have https://github.com/llvm/llvm-project/commit/ea72b0319d7b0f0c2fcf41d121afa5d031b319d5? unexpected error: -4007
|
| /linux/arch/arc/boot/dts/ |
| H A D | hsdk.dts | 159 * unexpected default value (it should divide by 1
|
| /linux/Documentation/arch/arm/ |
| H A D | kernel_mode_neon.rst | 86 instructions appearing in unexpected places if no special care is taken.
|