| /Linux-v5.4/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-v5.4/samples/mic/mpssd/ |
| D | mpss | 46 failure
56 failure
87 [ $RETVAL -ne 0 ] && failure || success
125 [ $RETVAL -ne 0 ] && failure || success
163 [ $RETVAL -ne 0 ] && failure || success
|
| /Linux-v5.4/tools/perf/tests/ |
| D | mem.c | 14 char failure[100]; in check() local
21 scnprintf(failure, sizeof failure, "unexpected %s", out); in check()
22 TEST_ASSERT_VAL(failure, !strcmp(string, out)); in check()
|
| /Linux-v5.4/drivers/media/platform/mtk-mdp/ |
| D | mtk_mdp_vpu.c | 37 vpu->failure = msg->status; in mtk_mdp_vpu_ipi_handler()
38 if (!vpu->failure) { in mtk_mdp_vpu_ipi_handler()
56 msg_id, vpu->failure); in mtk_mdp_vpu_ipi_handler()
105 if (!err && vpu->failure) in mtk_mdp_vpu_send_ap_ipi()
123 if (!err && vpu->failure) in mtk_mdp_vpu_init()
|
| D | mtk_mdp_vpu.h | 24 int32_t failure; member
|
| /Linux-v5.4/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-v5.4/scripts/ |
| D | Kconfig.include | 22 # $(failure,<command>)
24 failure = $(if-success,$(1),n,y)
35 $(error-if,$(failure,command -v $(CC)),compiler '$(CC)' not found)
36 $(error-if,$(failure,command -v $(LD)),linker '$(LD)' not found)
|
| /Linux-v5.4/drivers/hid/ |
| D | hid-uclogic-core.c | 177 goto failure; in uclogic_probe()
187 goto failure; in uclogic_probe()
195 goto failure; in uclogic_probe()
206 goto failure; in uclogic_probe()
212 goto failure; in uclogic_probe()
218 goto failure; in uclogic_probe()
222 failure: in uclogic_probe()
|
| /Linux-v5.4/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-v5.4/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_acp.c | 236 goto failure; in acp_hw_init()
242 goto failure; in acp_hw_init()
248 goto failure; in acp_hw_init()
345 goto failure; in acp_hw_init()
352 goto failure; in acp_hw_init()
372 goto failure; in acp_hw_init()
390 goto failure; in acp_hw_init()
400 failure: in acp_hw_init()
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | devres.rst | 29 sufficient bugs in ->remove and ->probe failure path. Well, yes,
37 initialization failure don't happen often enough to be noticeable.
38 Init failure path is worse because it's much less travelled while
42 and having half broken failure path implementation in ->probe() which
43 would leak resources or even cause oops when failure occurs. iomap
134 to better maintained higher layer. Also, as init failure path is
151 resources on failure. For example::
172 As resource acquisition failure usually means probe failure, constructs
174 layer) where interface function shouldn't have side effect on failure.
|
| /Linux-v5.4/net/sched/ |
| D | act_police.c | 110 goto failure; in tcf_police_init()
116 goto failure; in tcf_police_init()
127 goto failure; in tcf_police_init()
132 goto failure; in tcf_police_init()
141 goto failure; in tcf_police_init()
148 goto failure; in tcf_police_init()
208 failure: in tcf_police_init()
|
| /Linux-v5.4/drivers/media/platform/mtk-vcodec/ |
| D | vdec_vpu_if.c | 58 vpu->failure = msg->status; in vpu_dec_ipi_handler()
68 vpu->failure = 0; in vcodec_vpu_send_msg()
78 return vpu->failure; in vcodec_vpu_send_msg()
|
| D | venc_vpu_if.c | 54 vpu->failure = (msg->status != VENC_IPI_MSG_STATUS_OK); in vpu_enc_ipi_handler()
77 if (vpu->failure) in vpu_enc_send_msg()
94 vpu->failure = 0; in vpu_enc_init()
|
| D | venc_vpu_if.h | 31 int failure; member
|
| D | vdec_vpu_if.h | 28 int32_t failure; member
|
| /Linux-v5.4/drivers/macintosh/ |
| D | windfarm_fcu_controls.c | 171 unsigned char failure; in wf_fcu_fan_get_rpm() local
175 rc = wf_fcu_read_reg(pv, 0xb, &failure, 1); in wf_fcu_fan_get_rpm()
178 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_rpm()
227 unsigned char failure; in wf_fcu_fan_get_pwm() local
232 rc = wf_fcu_read_reg(pv, 0x2b, &failure, 1); in wf_fcu_fan_get_pwm()
235 if ((failure & (1 << fan->id)) != 0) in wf_fcu_fan_get_pwm()
|
| /Linux-v5.4/drivers/net/can/sja1000/ |
| D | kvaser_pci.c | 266 goto failure; in kvaser_pci_add_chan()
274 failure: in kvaser_pci_add_chan()
297 goto failure; in kvaser_pci_init_one()
363 failure: in kvaser_pci_init_one()
|
| /Linux-v5.4/arch/x86/mm/ |
| D | pat_rbtree.c | 134 goto failure; in memtype_rb_check_conflict()
148 goto failure; in memtype_rb_check_conflict()
159 failure: in memtype_rb_check_conflict()
|
| /Linux-v5.4/arch/arm/nwfpe/ |
| D | entry.S | 67 mov r4, lr @ save the failure-return addresses
83 reteq r4 @ no, return failure
|
| /Linux-v5.4/tools/testing/selftests/powerpc/tm/ |
| D | tm-trap.c | 219 : : : : failure, success); in ping()
221 failure: in ping()
|
| /Linux-v5.4/drivers/staging/ks7010/ |
| D | ks_hostif.c | 384 mic_failure->failure = 0; in hostif_data_indication_wpa()
387 if (mic_failure->failure == 0) { in hostif_data_indication_wpa()
388 mic_failure->failure = 1; in hostif_data_indication_wpa()
390 } else if (mic_failure->failure == 1) { in hostif_data_indication_wpa()
391 mic_failure->failure = 2; in hostif_data_indication_wpa()
459 priv->wpa.mic_failure.failure == 2) { in hostif_data_indication()
973 priv->wpa.mic_failure.failure); in hostif_mic_failure_confirm()
1161 priv->wpa.mic_failure.failure > 0) { in hostif_data_request()
1216 priv->wpa.mic_failure.failure > 0) { in hostif_data_request()
1223 if (priv->wpa.mic_failure.failure == 2) in hostif_data_request()
[all …]
|
| /Linux-v5.4/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-v5.4/Documentation/fault-injection/ |
| D | fault-injection.rst | 59 likelihood of failure injection, in percent.
63 Note that one-failure-per-hundred is a very high error rate
90 specifies the verbosity of the messages when failure is
92 log line per failure; '2' will print a call trace too -- useful
145 default is 'N', setting it to 'Y' will disable failure injections
238 Upon should_fail() returning true, client code should inject a failure:
368 allocation failure::
379 Same as above except to inject page allocation failure instead of slab
380 allocation failure::
|
| /Linux-v5.4/drivers/gpu/drm/amd/display/dc/gpio/ |
| D | gpio_service.c | 559 goto failure; in dal_ddc_open()
590 failure: in dal_ddc_open()
613 goto failure; in dal_ddc_change_mode()
622 failure: in dal_ddc_change_mode()
|
