| /Linux-v6.1/Documentation/dev-tools/kunit/ |
| D | usage.rst | 11 and then sets *expectations* for what should happen. For example:
25 nothing; no expectations are set, and therefore all expectations pass. On the
30 Expectations subsection
34 expectations about the behavior of a piece of code under test. When one or more
35 expectations fail, the test case fails and information about the failure is
51 expectations, the test case, ``add_test_basic`` will pass; if any one of these
52 expectations fails, the test case will fail.
55 continue to run, and try other expectations until the test case ends or is
59 To learn about more KUnit expectations, see Documentation/dev-tools/kunit/api/test.rst.
549 Exiting Early on Failed Expectations
|
| D | architecture.rst | 108 KUnit tests verify state using expectations/assertions.
109 All expectations/assertions are formatted as:
|
| /Linux-v6.1/include/kunit/ |
| D | try-catch.h | 39 * Assertions are like expectations, except they abort (call
43 * conclusion is a set of predicates, rather expectations, that must all be
|
| /Linux-v6.1/lib/kunit/ |
| D | kunit-example-test.c | 13 * makes a set EXPECTATIONs and ASSERTIONs about the behavior of some code; if
14 * any expectations or assertions are not met, the test fails; otherwise, the
25 * to test a piece of code, you set some expectations about what the in example_simple_test()
|
| /Linux-v6.1/Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 68 secondary by the expectations of contributors and maintainers.
70 Both the expertise expectations and decision-making are subject to
76 As a consequence, setting expertise expectations, making decisions and
|
| D | kernel-enforcement-statement.rst | 43 eliminate any uncertainty about our expectations regarding compliance or
|
| /Linux-v6.1/include/net/netfilter/ |
| D | nf_conntrack_expect.h | 3 * connection tracking expectations.
79 /* Allow to reuse expectations with the same tuples from different master
|
| D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
| /Linux-v6.1/net/netfilter/ |
| D | nf_conntrack_expect.c | 227 /* delete all expectations for this conntrack */
239 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
296 * conntracks. During the conntrack destruction, the expectations are
405 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
415 /* Race with expectations being used means we could have none to find; OK. */
422 hlist_for_each_entry(exp, &master_help->expectations, lnode) { in evict_oldest_expect()
|
| D | nf_conntrack_netbios_ns.c | 9 * requests by issuing permanent expectations (valid until
|
| /Linux-v6.1/net/ipv4/netfilter/ |
| D | nf_nat_h323.c | 187 /* Set expectations for NAT */ in nat_rtp_rtcp()
212 /* Run out of expectations */ in nat_rtp_rtcp()
214 net_notice_ratelimited("nf_nat_h323: out of expectations\n"); in nat_rtp_rtcp()
289 /* Set expectations for NAT */ in nat_t120()
328 /* Set expectations for NAT */ in nat_h245()
407 /* Set expectations for NAT */ in nat_q931()
489 /* Set expectations for NAT */ in nat_callforwarding()
|
| /Linux-v6.1/net/netfilter/ipvs/ |
| D | ip_vs_nfct.c | 21 * - FTP support (NAT), ability to support other NAT apps with expectations
22 * - to correctly create expectations for related NAT connections the proper
151 * expectations even if they use wildcard values, now we provide the in ip_vs_nfct_expect_callback()
|
| /Linux-v6.1/drivers/gpu/drm/i915/ |
| D | Kconfig.unstable | 16 verify that the uAPI meet their expectations. These uAPI should
|
| /Linux-v6.1/Documentation/ABI/stable/ |
| D | sysfs-acpi-pmprofile | 6 power management (and performance) requirement expectations
|
| /Linux-v6.1/drivers/soc/rockchip/ |
| D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /Linux-v6.1/drivers/platform/x86/intel/int3472/ |
| D | tps68470.c | 75 * our expectations
83 * A CLDB buffer that exists, but which does not match our expectations in skl_int3472_tps68470_calc_type()
|
| /Linux-v6.1/tools/testing/selftests/seccomp/ |
| D | seccomp_benchmark.c | 221 printf("Expectations:\n"); in main()
233 printf("Skipping constant action bitmap expectations: they appear unsupported.\n"); in main()
|
| /Linux-v6.1/Documentation/admin-guide/pm/ |
| D | intel_uncore_frequency_scaling.rst | 20 It is possible that users have different expectations of uncore performance and
|
| /Linux-v6.1/drivers/fsi/ |
| D | Kconfig | 26 to match old userspace expectations.
|
| /Linux-v6.1/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,glink.txt | 58 meet expectations of the remote.
|
| /Linux-v6.1/Documentation/driver-api/driver-model/ |
| D | device.rst | 111 strict expectations on when attributes get created. When a new device is
|
| /Linux-v6.1/Documentation/ |
| D | index.rst | 85 The following holds information on the kernel's expectations regarding the
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | dnotify.rst | 43 Implementation expectations (features and bugs :-))
|
| /Linux-v6.1/Documentation/maintainer/ |
| D | maintainer-entry-profile.rst | 10 their expectations and avoid common mistakes; maintainers may use these
|
| /Linux-v6.1/tools/testing/selftests/bpf/prog_tests/ |
| D | tailcalls.c | 298 * enforcement matches with expectations. JIT uses direct jump.
306 * enforcement matches with expectations. JIT uses indirect jump.
578 * enforcement matches with expectations when tailcall is preceded with
|
