| /linux/Documentation/maintainer/ |
| 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,
|
| A D | maintainer-entry-profile.rst | 10 their expectations and avoid common mistakes; maintainers may use these
|
| /linux/drivers/soc/rockchip/ |
| A D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /linux/Documentation/dev-tools/kunit/ |
| 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.
|
| A 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
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.
|
| /linux/Documentation/process/ |
| A 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
|
| A D | contribution-maturity-model.rst | 24 expectations for upstream community engagement aim to increase the
|
| A D | kernel-enforcement-statement.rst | 43 eliminate any uncertainty about our expectations regarding compliance or
|
| A D | researcher-guidelines.rst | 168 related to this document and the developer community's expectations,
|
| /linux/net/netfilter/ |
| A D | nf_conntrack_expect.c | 239 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
405 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
422 hlist_for_each_entry(exp, &master_help->expectations, lnode) { in evict_oldest_expect()
|
| A D | nf_conntrack_helper.c | 184 INIT_HLIST_HEAD(&help->expectations); in nf_ct_helper_ext_add()
|
| /linux/include/net/netfilter/ |
| A D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
| /linux/Documentation/devicetree/bindings/remoteproc/ |
| A D | qcom,glink-rpm-edge.yaml | 63 default intents available for the channel to meet expectations of the
|
| /linux/Documentation/admin-guide/ |
| A D | index.rst | 65 subsystems expectations will be found here.
|
| /linux/Documentation/ |
| A D | index.rst | 86 The following holds information on the kernel's expectations regarding the
|
| /linux/Documentation/filesystems/ |
| A D | dnotify.rst | 43 Implementation expectations (features and bugs :-))
|
| /linux/Documentation/driver-api/driver-model/ |
| A D | device.rst | 111 strict expectations on when attributes get created. When a new device is
|
| /linux/Documentation/devicetree/bindings/soc/qcom/ |
| A D | qcom,apr.yaml | 76 default intents available for the channel to meet expectations of the
|
| /linux/drivers/fsi/ |
| A D | Kconfig | 26 to match old userspace expectations.
|
| /linux/Documentation/ABI/testing/ |
| A D | configfs-tsm | 72 sure the number of writes matches expectations after reading
|
| /linux/Documentation/gpu/ |
| A D | automated_testing.rst | 113 How to update test expectations
|
| /linux/Documentation/admin-guide/pm/ |
| A D | intel_uncore_frequency_scaling.rst | 20 It is possible that users have different expectations of uncore performance and
|
| /linux/Documentation/admin-guide/laptops/ |
| A D | disk-shock-protection.rst | 75 milliseconds may raise expectations that cannot be satisfied in
|
| /linux/Documentation/bpf/ |
| A D | bpf_design_QA.rst | 208 lifecycle expectations as described in :ref:`BPF_kfunc_lifecycle_expectations`.
350 lifecycle expectations as the kfuncs themselves. See
|
| /linux/Documentation/firmware-guide/acpi/apei/ |
| A D | einj.rst | 182 creativity in using this feature expands beyond our expectations).
|