Home
last modified time | relevance | path

Searched refs:expectations (Results 1 – 25 of 36) sorted by relevance

12

/linux-6.1.9/Documentation/ABI/stable/
Dsysfs-acpi-pmprofile6 power management (and performance) requirement expectations
/linux-6.1.9/drivers/gpu/drm/i915/
DKconfig.unstable16 verify that the uAPI meet their expectations. These uAPI should
/linux-6.1.9/Documentation/dev-tools/kunit/
Dusage.rst11 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.
Darchitecture.rst108 KUnit tests verify state using expectations/assertions.
109 All expectations/assertions are formatted as:
Dtips.rst7 Exiting early on failed expectations
/linux-6.1.9/drivers/soc/rockchip/
DKconfig15 to make some of them conform to expectations of the kernel.
/linux-6.1.9/include/net/netfilter/
Dnf_conntrack_helper.h74 struct hlist_head expectations; member
/linux-6.1.9/net/netfilter/
Dnf_conntrack_expect.c239 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()
Dnf_conntrack_helper.c182 INIT_HLIST_HEAD(&help->expectations); in nf_ct_helper_ext_add()
Dnf_conntrack_sip.c812 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()
Dnf_nat_sip.c340 hlist_for_each_entry(pair_exp, &help->expectations, lnode) { in nf_nat_sip_expected()
/linux-6.1.9/Documentation/process/
Dcode-of-conduct-interpretation.rst68 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
Dkernel-enforcement-statement.rst43 eliminate any uncertainty about our expectations regarding compliance or
Dresearcher-guidelines.rst141 related to this document and the developer community's expectations,
/linux-6.1.9/Documentation/admin-guide/pm/
Dintel_uncore_frequency_scaling.rst20 It is possible that users have different expectations of uncore performance and
/linux-6.1.9/Documentation/
Dindex.rst85 The following holds information on the kernel's expectations regarding the
/linux-6.1.9/Documentation/devicetree/bindings/soc/qcom/
Dqcom,glink.txt58 meet expectations of the remote.
Dqcom,apr.yaml69 default intents available for the channel to meet expectations of the
/linux-6.1.9/drivers/fsi/
DKconfig26 to match old userspace expectations.
/linux-6.1.9/Documentation/filesystems/
Ddnotify.rst43 Implementation expectations (features and bugs :-))
/linux-6.1.9/Documentation/driver-api/driver-model/
Ddevice.rst111 strict expectations on when attributes get created. When a new device is
/linux-6.1.9/Documentation/maintainer/
Dmaintainer-entry-profile.rst10 their expectations and avoid common mistakes; maintainers may use these
/linux-6.1.9/Documentation/firmware-guide/acpi/apei/
Deinj.rst160 creativity in using this feature expands beyond our expectations).
/linux-6.1.9/Documentation/admin-guide/laptops/
Ddisk-shock-protection.rst75 milliseconds may raise expectations that cannot be satisfied in
/linux-6.1.9/Documentation/power/
Dpm_qos_interface.rst6 performance expectations by drivers, subsystems and user space applications on

12