| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/Documentation/maintainer/ |
| D | feature-and-driver-maintainers.rst | 12 populous) group. It provides tips and describes the expectations and
31 The exact expectations on the response time will vary by subsystem.
35 review delay of the subsystem maintainer. The resulting expectations
89 The previous section described the expectations of the maintainer,
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | usage.rst | 55 and then sets *expectations* for what should happen. For example:
69 nothing; no expectations are set, so all expectations pass. On the other hand
73 Expectations subsection
77 by setting expectations about the behavior of a piece of code under test; when
78 one or more of the expectations fail, the test case fails and information about
94 expectations, the test case, ``add_test_basic`` will pass; if any one of these
95 expectations fails, the test case will fail.
99 expectations until the test case ends or is otherwise terminated. This is as
102 To learn about more expectations supported by KUnit, see :doc:`api/test`.
|
| /kernel/linux/linux-6.6/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.
|
| D | architecture.rst | 108 KUnit tests verify state using expectations/assertions.
109 All expectations/assertions are formatted as:
116 - For expectations, the test is marked as failed and the failure is logged.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/include/net/netfilter/ |
| D | nf_conntrack_expect.h | 3 * connection tracking expectations.
79 /* Allow to reuse expectations with the same tuples from different master
|
| /kernel/linux/linux-5.10/include/net/netfilter/ |
| D | nf_conntrack_expect.h | 3 * connection tracking expectations.
79 /* Allow to reuse expectations with the same tuples from different master
|
| /kernel/linux/linux-5.10/net/netfilter/ |
| D | nf_conntrack_expect.c | 211 /* delete all expectations for this conntrack */
223 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
280 * conntracks. During the conntrack destruction, the expectations are
388 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
397 /* Race with expectations being used means we could have none to find; OK. */
404 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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/lib/kunit/ |
| D | kunit-example-test.c | 14 * makes a set EXPECTATIONs and ASSERTIONs about the behavior of some code; if
15 * any expectations or assertions are not met, the test fails; otherwise, the
26 * to test a piece of code, you set some expectations about what the in example_simple_test()
|
| /kernel/linux/linux-5.10/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()
341 /* Set expectations for NAT */ in nat_h245()
433 /* Set expectations for NAT */ in nat_q931()
528 /* Set expectations for NAT */ in nat_callforwarding()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-acpi-pmprofile | 6 power management (and performance) requirement expectations
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/ |
| D | Kconfig.unstable | 16 verify that the uAPI meet their expectations. These uAPI should
|
| /kernel/linux/linux-5.10/drivers/soc/rockchip/ |
| D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /kernel/linux/linux-6.6/drivers/soc/rockchip/ |
| D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /kernel/linux/linux-6.6/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()
|