Searched refs:catch (Results 1 – 25 of 67) sorted by relevance
123
| /linux-5.19.10/lib/kunit/ |
| D | try-catch-impl.h | 20 kunit_try_catch_func_t catch) in kunit_try_catch_init() argument
24 try_catch->catch = catch; in kunit_try_catch_init()
|
| D | try-catch.c | 72 try_catch->catch(try_catch->context); in kunit_try_catch_run()
96 try_catch->catch(try_catch->context); in kunit_try_catch_run()
|
| D | Makefile | 7 try-catch.o \
|
| /linux-5.19.10/tools/testing/kunit/test_data/ |
| D | test_kernel_panic_interrupt.log | 13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
|
| D | test_config_printk_time.log | 13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
|
| D | test_output_with_prefix_isolated_correctly.log | 14 [ 0.060000] # Subtest: kunit-try-catch-test
18 [ 0.060000] ok 2 - kunit-try-catch-test
|
| D | test_pound_no_prefix.log | 15 # Subtest: kunit-try-catch-test
19 ok 2 - kunit-try-catch-test
|
| D | test_pound_sign.log | 15 [ 0.060000] # Subtest: kunit-try-catch-test
19 [ 0.060000] ok 2 - kunit-try-catch-test
|
| D | test_multiple_prefixes.log | 13 [ 0.060000][ T1] # Subtest: kunit-try-catch-test
17 [ 0.060000][ T1] ok 2 - kunit-try-catch-test
|
| D | test_interrupted_tap_output.log | 19 [ 0.060000] # Subtest: kunit-try-catch-test
23 [ 0.060000] ok 2 - kunit-try-catch-test
|
| /linux-5.19.10/include/kunit/ |
| D | try-catch.h | 52 kunit_try_catch_func_t catch; member
|
| /linux-5.19.10/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 46 performance but will catch some internal issues.
139 performance but will catch some internal issues.
151 performance but will catch some internal issues.
|
| /linux-5.19.10/arch/xtensa/ |
| D | Kconfig.debug | 31 It is easy to make wrong hardware configuration, this test should catch it early.
|
| /linux-5.19.10/Documentation/devicetree/bindings/leds/ |
| D | leds-gpio.yaml | 23 # node name to at least catch some child nodes.
|
| /linux-5.19.10/Documentation/dev-tools/ |
| D | ubsan.rst | 6 UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
|
| /linux-5.19.10/Documentation/powerpc/ |
| D | kasan.txt | 23 - It would be good to support inline instrumentation so as to be able to catch
|
| /linux-5.19.10/Documentation/trace/ |
| D | stm.rst | 70 catch-all entry "default" will be used, if it exists. This entry also
115 node, the stm core will use the catch-all entry "default", if one
|
| /linux-5.19.10/Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 58 flowing, then the tail pointer can catch up to the hardware pointer.
70 RX traffic is flowing, then the head pointer can catch up to the tail
119 pointer will catch up to the head, notice the not-empty condition,
|
| /linux-5.19.10/drivers/nvdimm/ |
| D | Kconfig | 113 otherwise helps catch build errors induced by changes to the
|
| /linux-5.19.10/tools/testing/selftests/bpf/ |
| D | vmtest.sh | 397 catch() function
|
| /linux-5.19.10/Documentation/gpu/ |
| D | drm-usage-stats.rst | 82 implementation easier, but are required to catch up with the previously reported
|
| /linux-5.19.10/Documentation/PCI/ |
| D | acpi-info.rst | 66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 158 As such, we cannot catch all types of corruption that can occur within a block
168 marks the object being read as EFSCORRUPTED. The caller needs to catch this
186 error for the higher layers to catch.
|
| /linux-5.19.10/Documentation/scheduler/ |
| D | sched-domains.rst | 80 the sched domains which should catch most possible errors (described above). It
|
| /linux-5.19.10/Documentation/bpf/ |
| D | prog_cgroup_sysctl.rst | 106 environment, for example to monitor sysctl usage or catch unreasonable values
|
123