Home
last modified time | relevance | path

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

12

/linux/Documentation/ABI/stable/
A Dsysfs-acpi-pmprofile6 power management (and performance) requirement expectations
/linux/drivers/gpu/drm/i915/
A DKconfig.unstable16 verify that the uAPI meet their expectations. These uAPI should
/linux/Documentation/dev-tools/kunit/
A Dusage.rst55 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
A Dtips.rst7 Exiting early on failed expectations
/linux/Documentation/process/
A 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
A Dkernel-enforcement-statement.rst43 eliminate any uncertainty about our expectations regarding compliance or
A Dbotching-up-ioctls.rst100 Check that the error code matches your expectations. And finally make sure
A D5.Posting.rst11 document will attempt to cover these expectations in reasonable detail;
/linux/drivers/soc/rockchip/
A DKconfig15 to make some of them conform to expectations of the kernel.
/linux/net/netfilter/
A 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()
A Dnf_conntrack_helper.c205 INIT_HLIST_HEAD(&help->expectations); in nf_ct_helper_ext_add()
A 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()
A Dnf_nat_sip.c340 hlist_for_each_entry(pair_exp, &help->expectations, lnode) { in nf_nat_sip_expected()
/linux/include/net/netfilter/
A Dnf_conntrack_helper.h74 struct hlist_head expectations; member
/linux/Documentation/devicetree/bindings/soc/qcom/
A Dqcom,glink.txt58 meet expectations of the remote.
/linux/drivers/fsi/
A DKconfig26 to match old userspace expectations.
/linux/Documentation/filesystems/
A Ddnotify.rst43 Implementation expectations (features and bugs :-))
/linux/Documentation/driver-api/driver-model/
A Ddevice.rst111 strict expectations on when attributes get created. When a new device is
/linux/Documentation/
A Dindex.rst44 The following holds information on the kernel's expectations regarding the
/linux/Documentation/maintainer/
A Dmaintainer-entry-profile.rst10 their expectations and avoid common mistakes; maintainers may use these
/linux/Documentation/firmware-guide/acpi/apei/
A Deinj.rst160 creativity in using this feature expands beyond our expectations).
/linux/Documentation/admin-guide/laptops/
A Ddisk-shock-protection.rst75 milliseconds may raise expectations that cannot be satisfied in
/linux/Documentation/power/
A Dpm_qos_interface.rst6 performance expectations by drivers, subsystems and user space applications on
/linux/Documentation/arm64/
A Dacpi_object_usage.rst5 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
/linux/Documentation/firmware-guide/acpi/
A Dgpio-properties.rst68 and polarity settings. The table below shows the expectations:

Completed in 41 milliseconds

12