| /linux/Documentation/maintainer/ |
| H A 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
100 The previous section described the expectations of the maintainer,
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | tailcalls.c | 393 * enforcement matches with expectations. JIT uses direct jump.
401 * enforcement matches with expectations. JIT uses indirect jump.
673 * enforcement matches with expectations when tailcall is preceded with
983 * limit enforcement matches with expectations when tailcall is preceded with
992 * limit enforcement matches with expectations when tailcall is preceded with
1001 * call limit enforcement matches with expectations when tailcall is preceded
1010 * call limit enforcement matches with expectations when tailcall is preceded
1423 * call limit enforcement matches with expectations when tailcalls are preceded
1437 * tail call limit enforcement matches with expectations when tailcalls are
1447 * call limit enforcement matches with expectations when tailcalls are preceded
[all …]
|
| /linux/include/kunit/ |
| H A D | try-catch.h | 37 * Assertions are like expectations, except they abort (call
41 * conclusion is a set of predicates, rather expectations, that must all be
|
| /linux/include/net/netfilter/ |
| H A D | nf_conntrack_expect.h | 3 * connection tracking expectations.
79 /* Allow to reuse expectations with the same tuples from different master
|
| H A D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
| /linux/net/netfilter/ |
| H A 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()
|
| H A D | nf_conntrack_netbios_ns.c | 9 * requests by issuing permanent expectations (valid until
|
| /linux/net/ipv4/netfilter/ |
| H A 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/Documentation/dev-tools/kunit/ |
| H A 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.
|
| /linux/net/netfilter/ipvs/ |
| H A 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/lib/kunit/ |
| H A 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()
478 * and expectations.
|
| /linux/drivers/soc/rockchip/ |
| H A D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /linux/drivers/platform/x86/intel/int3472/ |
| H A 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/Documentation/devicetree/bindings/remoteproc/ |
| H A D | qcom,glink-rpm-edge.yaml | 63 default intents available for the channel to meet expectations of the
|
| /linux/tools/testing/selftests/seccomp/ |
| H A D | seccomp_benchmark.c | 276 ksft_print_msg("Expectations:\n"); in main()
290 ksft_print_msg("Skipping constant action bitmap expectations: they appear unsupported.\n"); in main()
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | test_bpftool_map.sh | 251 # Function to test map access with configurable write expectations
280 # Function to test map access with configurable write expectations
|
| /linux/drivers/fsi/ |
| H A D | Kconfig | 26 to match old userspace expectations.
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | device.rst | 111 strict expectations on when attributes get created. When a new device is
|
| /linux/Documentation/filesystems/ |
| H A D | dnotify.rst | 43 Implementation expectations (features and bugs :-))
|
| /linux/Documentation/process/ |
| H A D | contribution-maturity-model.rst | 24 expectations for upstream community engagement aim to increase the
|
| H A D | kernel-enforcement-statement.rst | 43 eliminate any uncertainty about our expectations regarding compliance or
|
| /linux/Documentation/ |
| H A D | index.rst | 86 The following holds information on the kernel's expectations regarding the
|
| /linux/drivers/clk/starfive/ |
| H A D | clk-starfive-jh7110-pll.c | 335 /* if the parent rate doesn't match our expectations the presets won't work */ in jh7110_pll_determine_rate()
364 /* if the parent rate doesn't match our expectations the presets won't work */ in jh7110_pll_set_rate()
|
| /linux/Documentation/devicetree/bindings/soc/qcom/ |
| H A D | qcom,apr.yaml | 76 default intents available for the channel to meet expectations of the
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-tsm-report | 72 sure the number of writes matches expectations after reading
|