Home
last modified time | relevance | path

Searched refs:catch (Results 1 – 25 of 73) sorted by relevance

123

/linux-6.3-rc2/lib/kunit/
A Dtry-catch-impl.h20 kunit_try_catch_func_t catch) in kunit_try_catch_init() argument
24 try_catch->catch = catch; in kunit_try_catch_init()
A Dtry-catch.c72 try_catch->catch(try_catch->context); in kunit_try_catch_run()
96 try_catch->catch(try_catch->context); in kunit_try_catch_run()
A DMakefile8 try-catch.o \
/linux-6.3-rc2/tools/testing/kunit/test_data/
A Dtest_kernel_panic_interrupt.log13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
A Dtest_config_printk_time.log13 [ 0.060000] # Subtest: kunit-try-catch-test
17 [ 0.060000] ok 2 - kunit-try-catch-test
A Dtest_pound_no_prefix.log15 # Subtest: kunit-try-catch-test
19 ok 2 - kunit-try-catch-test
A Dtest_pound_sign.log15 [ 0.060000] # Subtest: kunit-try-catch-test
19 [ 0.060000] ok 2 - kunit-try-catch-test
A Dtest_output_with_prefix_isolated_correctly.log14 [ 0.060000] # Subtest: kunit-try-catch-test
18 [ 0.060000] ok 2 - kunit-try-catch-test
A Dtest_multiple_prefixes.log13 [ 0.060000][ T1] # Subtest: kunit-try-catch-test
17 [ 0.060000][ T1] ok 2 - kunit-try-catch-test
A Dtest_interrupted_tap_output.log19 [ 0.060000] # Subtest: kunit-try-catch-test
23 [ 0.060000] ok 2 - kunit-try-catch-test
/linux-6.3-rc2/include/kunit/
A Dtry-catch.h52 kunit_try_catch_func_t catch; member
/linux-6.3-rc2/tools/testing/selftests/bpf/
A Dverify_sig_setup.sh63 catch() function
A Dvmtest.sh316 catch() function
/linux-6.3-rc2/drivers/gpu/drm/i915/
A DKconfig.debug46 performance but will catch some internal issues.
139 performance but will catch some internal issues.
151 performance but will catch some internal issues.
/linux-6.3-rc2/arch/xtensa/
A DKconfig.debug31 It is easy to make wrong hardware configuration, this test should catch it early.
/linux-6.3-rc2/Documentation/devicetree/bindings/leds/
A Dleds-gpio.yaml23 # node name to at least catch some child nodes.
/linux-6.3-rc2/Documentation/gpu/
A Ddrm-usage-stats.rst82 implementation easier, but are required to catch up with the previously reported
115 implementation easier, but are required to catch up with the previously reported
/linux-6.3-rc2/Documentation/dev-tools/
A Dubsan.rst6 UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
/linux-6.3-rc2/Documentation/powerpc/
A Dkasan.txt23 - It would be good to support inline instrumentation so as to be able to catch
/linux-6.3-rc2/Documentation/dev-tools/kunit/
A Darchitecture.rst103 `lib/kunit/try-catch.c <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/lib…
/linux-6.3-rc2/Documentation/trace/
A Dstm.rst70 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-6.3-rc2/Documentation/networking/device_drivers/ethernet/toshiba/
A Dspider_net.rst58 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-6.3-rc2/drivers/nvdimm/
A DKconfig132 otherwise helps catch build errors induced by changes to the
/linux-6.3-rc2/Documentation/PCI/
A Dacpi-info.rst66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
/linux-6.3-rc2/Documentation/filesystems/
A Dxfs-self-describing-metadata.rst158 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.

Completed in 27 milliseconds

123