Searched refs:expectations (Results 1 – 25 of 32) sorted by relevance
12
| /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/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
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-5.10/drivers/soc/rockchip/ |
| D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /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
|
| D | kernel-enforcement-statement.rst | 43 eliminate any uncertainty about our expectations regarding compliance or
|
| D | botching-up-ioctls.rst | 100 Check that the error code matches your expectations. And finally make sure
|
| D | 5.Posting.rst | 11 document will attempt to cover these expectations in reasonable detail;
|
| /kernel/linux/linux-5.10/include/net/netfilter/ |
| D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
| /kernel/linux/linux-5.10/net/netfilter/ |
| D | nf_conntrack_expect.c | 223 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
388 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
404 hlist_for_each_entry(exp, &master_help->expectations, lnode) { in evict_oldest_expect()
|
| D | nf_conntrack_helper.c | 205 INIT_HLIST_HEAD(&help->expectations); in nf_ct_helper_ext_add()
|
| D | nf_conntrack_sip.c | 812 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in refresh_signalling_expectation()
835 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in flush_expectations()
|
| D | nf_nat_sip.c | 340 hlist_for_each_entry(pair_exp, &help->expectations, lnode) { in nf_nat_sip_expected()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,glink.txt | 58 meet expectations of the remote.
|
| /kernel/linux/linux-5.10/drivers/fsi/ |
| D | Kconfig | 26 to match old userspace expectations.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
| D | device.rst | 100 strict expectations on when attributes get created. When a new device is
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | dnotify.rst | 43 Implementation expectations (features and bugs :-))
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | index.rst | 44 The following holds information on the kernel's expectations regarding the
|
| /kernel/linux/linux-5.10/Documentation/maintainer/ |
| D | maintainer-entry-profile.rst | 10 their expectations and avoid common mistakes; maintainers may use these
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/apei/ |
| D | einj.rst | 160 creativity in using this feature expands beyond our expectations).
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 75 milliseconds may raise expectations that cannot be satisfied in
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | gpio-properties.rst | 68 and polarity settings. The table below shows the expectations:
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | pm_qos_interface.rst | 6 performance expectations by drivers, subsystems and user space applications on
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | acpi_object_usage.rst | 5 The expectations of individual ACPI tables are discussed in the list that
434 The expectations on individual ACPI objects that are likely to be used are
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | atomic_ops.rst | 572 Spinlocks and rwlocks have memory barrier expectations as well.
|
12