| /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,
|
| H A D | maintainer-entry-profile.rst | 10 their expectations and avoid common mistakes; maintainers may use these
|
| /linux/drivers/soc/rockchip/ |
| H A D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /linux/Documentation/dev-tools/kunit/ |
| H 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.
|
| 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/ |
| H 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()
|
| H A D | nf_conntrack_helper.c | 184 INIT_HLIST_HEAD(&help->expectations); in nf_ct_helper_ext_add()
|
| H A D | nf_nat_sip.c | 340 hlist_for_each_entry(pair_exp, &help->expectations, lnode) { in nf_nat_sip_expected()
|
| /linux/include/net/netfilter/ |
| H A D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
| /linux/Documentation/ |
| H A D | index.rst | 86 The following holds information on the kernel's expectations regarding the
|
| /linux/Documentation/filesystems/ |
| H A D | dnotify.rst | 43 Implementation expectations (features and bugs :-))
|
| /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/drivers/fsi/ |
| H A D | Kconfig | 26 to match old userspace expectations.
|
| /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
|
| H A D | researcher-guidelines.rst | 168 related to this document and the developer community's expectations,
|
| H A D | botching-up-ioctls.rst | 100 Check that the error code matches your expectations. And finally make sure
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-tsm | 72 sure the number of writes matches expectations after reading
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_uncore_frequency_scaling.rst | 20 It is possible that users have different expectations of uncore performance and
|
| /linux/Documentation/bpf/ |
| H 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/admin-guide/laptops/ |
| H A D | disk-shock-protection.rst | 75 milliseconds may raise expectations that cannot be satisfied in
|
| /linux/Documentation/firmware-guide/acpi/apei/ |
| H A D | einj.rst | 182 creativity in using this feature expands beyond our expectations).
|
| /linux/Documentation/power/ |
| H A D | pm_qos_interface.rst | 6 performance expectations by drivers, subsystems and user space applications on
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | gpio-properties.rst | 68 and polarity settings. The table below shows the expectations:
|
| /linux/Documentation/arch/arm64/ |
| H A D | acpi_object_usage.rst | 5 The expectations of individual ACPI tables are discussed in the list that
505 The expectations on individual ACPI objects that are likely to be used are
|