| /Linux-v4.19/samples/bpf/ |
| D | test_lwt_bpf.sh | 134 function failure { function
144 failure "test_ctx xmit: packets are dropped"
160 failure "test_ctx out: packets are dropped"
176 failure "test_ctx out: packets are dropped"
200 failure "test_data ${1}: packets are dropped"
213 failure "test_data in: packets are dropped"
231 failure "test_cb ${1}: packets are dropped"
247 failure "test_cb in: packets are dropped"
271 failure "test_drop_all ${1}: Unexpected success of ping"
284 failure "test_drop_all in: Unexpected success of ping"
[all …]
|
| /Linux-v4.19/samples/mic/mpssd/ |
| D | mpss | 57 failure
67 failure
98 [ $RETVAL -ne 0 ] && failure || success
136 [ $RETVAL -ne 0 ] && failure || success
174 [ $RETVAL -ne 0 ] && failure || success
|
| /Linux-v4.19/tools/perf/tests/ |
| D | mem.c | 12 char failure[100]; in check() local
19 scnprintf(failure, sizeof failure, "unexpected %s", out); in check()
20 TEST_ASSERT_VAL(failure, !strcmp(string, out)); in check()
|
| /Linux-v4.19/drivers/media/platform/mtk-mdp/ |
| D | mtk_mdp_vpu.c | 45 vpu->failure = msg->status; in mtk_mdp_vpu_ipi_handler()
46 if (!vpu->failure) { in mtk_mdp_vpu_ipi_handler()
64 msg_id, vpu->failure); in mtk_mdp_vpu_ipi_handler()
113 if (!err && vpu->failure) in mtk_mdp_vpu_send_ap_ipi()
131 if (!err && vpu->failure) in mtk_mdp_vpu_init()
|
| D | mtk_mdp_vpu.h | 32 int32_t failure; member
|
| /Linux-v4.19/drivers/gpu/drm/amd/amdkfd/ |
| D | kfd_events.c | 911 memory_exception_data.failure.NotPresent = 1; in kfd_signal_iommu_event()
912 memory_exception_data.failure.NoExecute = 0; in kfd_signal_iommu_event()
913 memory_exception_data.failure.ReadOnly = 0; in kfd_signal_iommu_event()
915 memory_exception_data.failure.NotPresent = 0; in kfd_signal_iommu_event()
918 memory_exception_data.failure.ReadOnly = 1; in kfd_signal_iommu_event()
920 memory_exception_data.failure.ReadOnly = 0; in kfd_signal_iommu_event()
923 memory_exception_data.failure.NoExecute = 1; in kfd_signal_iommu_event()
925 memory_exception_data.failure.NoExecute = 0; in kfd_signal_iommu_event()
932 memory_exception_data.failure.NotPresent, in kfd_signal_iommu_event()
933 memory_exception_data.failure.NoExecute, in kfd_signal_iommu_event()
[all …]
|
| /Linux-v4.19/arch/m68k/ifpsp060/ |
| D | os.S | 84 | d1 - 0 = success, !0 = failure
115 | d1 - 0 = success, !0 = failure
147 | d1 - 0 = success, !0 = failure
170 | d1 - 0 = success, !0 = failure
181 | d1 - 0 = success, !0 = failure
206 | d1 - 0 = success, !0 = failure
217 | d1 - 0 = success, !0 = failure
241 | d1 - 0 = success, !0 = failure
263 | d1 - 0 = success, !0 = failure
287 | d1 - 0 = success, !0 = failure
|
| /Linux-v4.19/Documentation/driver-model/ |
| D | devres.txt | 27 sufficient bugs in ->remove and ->probe failure path. Well, yes,
35 initialization failure don't happen often enough to be noticeable.
36 Init failure path is worse because it's much less travelled while
40 and having half broken failure path implementation in ->probe() which
41 would leak resources or even cause oops when failure occurs. iomap
132 to better maintained higher layer. Also, as init failure path is
142 resources on failure. For example,
163 As resource acquisition failure usually means probe failure, constructs
165 layer) where interface function shouldn't have side effect on failure.
|
| /Linux-v4.19/drivers/media/platform/mtk-vcodec/ |
| D | vdec_vpu_if.c | 66 vpu->failure = msg->status; in vpu_dec_ipi_handler()
76 vpu->failure = 0; in vcodec_vpu_send_msg()
86 return vpu->failure; in vcodec_vpu_send_msg()
|
| D | venc_vpu_if.c | 63 vpu->failure = (msg->status != VENC_IPI_MSG_STATUS_OK); in vpu_enc_ipi_handler()
86 if (vpu->failure) in vpu_enc_send_msg()
103 vpu->failure = 0; in vpu_enc_init()
|
| D | vdec_vpu_if.h | 36 int32_t failure; member
|
| D | venc_vpu_if.h | 40 int failure; member
|
| /Linux-v4.19/net/sched/ |
| D | act_police.c | 129 goto failure; in tcf_police_init()
135 goto failure; in tcf_police_init()
145 goto failure; in tcf_police_init()
150 goto failure; in tcf_police_init()
199 failure: in tcf_police_init()
|
| /Linux-v4.19/drivers/macintosh/ |
| D | windfarm_fcu_controls.c | 172 unsigned char failure; in wf_fcu_fan_get_rpm() local
176 rc = wf_fcu_read_reg(pv, 0xb, &failure, 1); in wf_fcu_fan_get_rpm()
179 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_rpm()
228 unsigned char failure; in wf_fcu_fan_get_pwm() local
233 rc = wf_fcu_read_reg(pv, 0x2b, &failure, 1); in wf_fcu_fan_get_pwm()
236 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_pwm()
|
| /Linux-v4.19/drivers/net/can/sja1000/ |
| D | kvaser_pci.c | 277 goto failure; in kvaser_pci_add_chan()
285 failure: in kvaser_pci_add_chan()
308 goto failure; in kvaser_pci_init_one()
374 failure: in kvaser_pci_init_one()
|
| /Linux-v4.19/arch/arm/nwfpe/ |
| D | entry.S | 79 mov r4, lr @ save the failure-return addresses
95 reteq r4 @ no, return failure
|
| /Linux-v4.19/tools/testing/selftests/powerpc/tm/ |
| D | tm-trap.c | 219 : : : : failure, success); in ping()
221 failure: in ping()
|
| /Linux-v4.19/arch/x86/mm/ |
| D | pat_rbtree.c | 147 goto failure; in memtype_rb_check_conflict()
161 goto failure; in memtype_rb_check_conflict()
172 failure: in memtype_rb_check_conflict()
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | init.rst | 6 Some high-level reasons for failure (listed roughly in order of execution)
41 Please extend this explanation whenever you find new failure causes
47 which can then store the ``kernel_execve()`` result value and on failure
|
| /Linux-v4.19/drivers/staging/ks7010/ |
| D | ks_hostif.c | 317 mic_failure->failure = 0; in hostif_data_indication_wpa()
320 if (mic_failure->failure == 0) { in hostif_data_indication_wpa()
321 mic_failure->failure = 1; in hostif_data_indication_wpa()
323 } else if (mic_failure->failure == 1) { in hostif_data_indication_wpa()
324 mic_failure->failure = 2; in hostif_data_indication_wpa()
392 priv->wpa.mic_failure.failure == 2) { in hostif_data_indication()
906 priv->wpa.mic_failure.failure); in hostif_mic_failure_confirm()
1096 priv->wpa.mic_failure.failure > 0) { in hostif_data_request()
1148 priv->wpa.mic_failure.failure > 0) { in hostif_data_request()
1155 if (priv->wpa.mic_failure.failure == 2) in hostif_data_request()
[all …]
|
| /Linux-v4.19/Documentation/fault-injection/ |
| D | fault-injection.txt | 57 likelihood of failure injection, in percent.
60 Note that one-failure-per-hundred is a very high error rate
86 specifies the verbosity of the messages when failure is
88 log line per failure; '2' will print a call trace too -- useful
137 default is 'N', setting it to 'Y' will disable failure injections
227 Upon should_fail() returning true, client code should inject a failure.
357 allocation failure.
368 Same as above except to inject page allocation failure instead of slab
369 allocation failure.
|
| /Linux-v4.19/drivers/gpu/drm/amd/display/dc/gpio/ |
| D | gpio_service.c | 497 goto failure; in dal_ddc_open()
528 failure: in dal_ddc_open()
551 goto failure; in dal_ddc_change_mode()
560 failure: in dal_ddc_change_mode()
|
| /Linux-v4.19/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /Linux-v4.19/drivers/net/ethernet/micrel/ |
| D | ks8695net.c | 1395 goto failure; in ks8695_probe()
1405 goto failure; in ks8695_probe()
1413 goto failure; in ks8695_probe()
1426 goto failure; in ks8695_probe()
1436 goto failure; in ks8695_probe()
1477 goto failure; in ks8695_probe()
1539 goto failure; in ks8695_probe()
1546 failure: in ks8695_probe()
|
| /Linux-v4.19/Documentation/powerpc/ |
| D | transactional_memory.txt | 60 abort handler can check the cause of the failure, and retry.
78 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
85 effects will be persistent, independent of transaction success or failure. No
92 failure before entering the kernel (which may produce different failure codes).
197 presented). The transaction cannot then be continued and will take the failure
|
