Home
last modified time | relevance | path

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

/Linux-v4.19/Documentation/ABI/stable/
Dsysfs-acpi-pmprofile6 power management (and performance) requirement expectations
/Linux-v4.19/drivers/soc/rockchip/
DKconfig14 to make some of them conform to expectations of the kernel.
/Linux-v4.19/include/net/netfilter/
Dnf_conntrack_helper.h67 struct hlist_head expectations; member
/Linux-v4.19/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.rst41 eliminate any uncertainty about our expectations regarding compliance or
D5.Posting.rst11 document will attempt to cover these expectations in reasonable detail;
D4.Coding.rst375 the expectations for new code are higher than they were in the past;
/Linux-v4.19/net/netfilter/
Dnf_conntrack_expect.c224 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
380 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
396 hlist_for_each_entry(exp, &master_help->expectations, lnode) { in evict_oldest_expect()
Dnf_conntrack_helper.c201 INIT_HLIST_HEAD(&help->expectations); in nf_ct_helper_ext_add()
Dnf_conntrack_sip.c806 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in refresh_signalling_expectation()
829 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in flush_expectations()
Dnf_conntrack_core.c1618 if (ct->master || (help && !hlist_empty(&help->expectations))) in nf_conntrack_alter_reply()
Dnf_conntrack_netlink.c2905 hlist_for_each_entry_rcu(exp, &help->expectations, lnode) { in ctnetlink_exp_ct_dump_table()
/Linux-v4.19/drivers/fsi/
DKconfig25 to match old userspace expectations.
/Linux-v4.19/Documentation/devicetree/bindings/soc/qcom/
Dqcom,glink.txt53 meet expectations of the remote.
/Linux-v4.19/Documentation/driver-model/
Ddevice.txt97 strict expectations on when attributes get created. When a new device is
/Linux-v4.19/Documentation/filesystems/
Ddnotify.txt38 Implementation expectations (features and bugs :-))
/Linux-v4.19/Documentation/acpi/apei/
Deinj.txt152 creativity in using this feature expands beyond our expectations).
/Linux-v4.19/Documentation/laptops/
Ddisk-shock-protection.txt74 milliseconds may raise expectations that cannot be satisfied in
/Linux-v4.19/Documentation/power/
Dpm_qos_interface.txt4 performance expectations by drivers, subsystems and user space applications on
/Linux-v4.19/Documentation/arm64/
Dacpi_object_usage.txt3 The expectations of individual ACPI tables are discussed in the list that
321 The expectations on individual ACPI objects that are likely to be used are
Darm-acpi.txt484 Detailed expectations for ACPI tables and object are listed in the file
/Linux-v4.19/Documentation/ioctl/
Dbotching-up-ioctls.txt99 Check that the error code matches your expectations. And finally make sure
/Linux-v4.19/Documentation/core-api/
Datomic_ops.rst572 Spinlocks and rwlocks have memory barrier expectations as well.
/Linux-v4.19/Documentation/x86/
Dboot.txt8 expectations in the PC industry caused by the effective demise of
/Linux-v4.19/Documentation/block/
Dbiodoc.txt379 The following were some of the goals and expectations considered in the