Searched refs:expectations (Results 1 – 25 of 36) sorted by relevance
12
/linux-6.1.9/Documentation/ABI/stable/ |
D | sysfs-acpi-pmprofile | 6 power management (and performance) requirement expectations
|
/linux-6.1.9/drivers/gpu/drm/i915/ |
D | Kconfig.unstable | 16 verify that the uAPI meet their expectations. These uAPI should
|
/linux-6.1.9/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 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:
|
D | tips.rst | 7 Exiting early on failed expectations
|
/linux-6.1.9/drivers/soc/rockchip/ |
D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
/linux-6.1.9/include/net/netfilter/ |
D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
/linux-6.1.9/net/netfilter/ |
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()
|
D | nf_conntrack_helper.c | 182 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()
|
/linux-6.1.9/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 | researcher-guidelines.rst | 141 related to this document and the developer community's expectations,
|
/linux-6.1.9/Documentation/admin-guide/pm/ |
D | intel_uncore_frequency_scaling.rst | 20 It is possible that users have different expectations of uncore performance and
|
/linux-6.1.9/Documentation/ |
D | index.rst | 85 The following holds information on the kernel's expectations regarding the
|
/linux-6.1.9/Documentation/devicetree/bindings/soc/qcom/ |
D | qcom,glink.txt | 58 meet expectations of the remote.
|
D | qcom,apr.yaml | 69 default intents available for the channel to meet expectations of the
|
/linux-6.1.9/drivers/fsi/ |
D | Kconfig | 26 to match old userspace expectations.
|
/linux-6.1.9/Documentation/filesystems/ |
D | dnotify.rst | 43 Implementation expectations (features and bugs :-))
|
/linux-6.1.9/Documentation/driver-api/driver-model/ |
D | device.rst | 111 strict expectations on when attributes get created. When a new device is
|
/linux-6.1.9/Documentation/maintainer/ |
D | maintainer-entry-profile.rst | 10 their expectations and avoid common mistakes; maintainers may use these
|
/linux-6.1.9/Documentation/firmware-guide/acpi/apei/ |
D | einj.rst | 160 creativity in using this feature expands beyond our expectations).
|
/linux-6.1.9/Documentation/admin-guide/laptops/ |
D | disk-shock-protection.rst | 75 milliseconds may raise expectations that cannot be satisfied in
|
/linux-6.1.9/Documentation/power/ |
D | pm_qos_interface.rst | 6 performance expectations by drivers, subsystems and user space applications on
|
12