Searched refs:expectations (Results 1 – 25 of 25) sorted by relevance
/Linux-v4.19/Documentation/ABI/stable/ |
D | sysfs-acpi-pmprofile | 6 power management (and performance) requirement expectations
|
/Linux-v4.19/drivers/soc/rockchip/ |
D | Kconfig | 14 to make some of them conform to expectations of the kernel.
|
/Linux-v4.19/include/net/netfilter/ |
D | nf_conntrack_helper.h | 67 struct hlist_head expectations; member
|
/Linux-v4.19/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 | 41 eliminate any uncertainty about our expectations regarding compliance or
|
D | 5.Posting.rst | 11 document will attempt to cover these expectations in reasonable detail;
|
D | 4.Coding.rst | 375 the expectations for new code are higher than they were in the past;
|
/Linux-v4.19/net/netfilter/ |
D | nf_conntrack_expect.c | 224 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()
|
D | nf_conntrack_helper.c | 201 INIT_HLIST_HEAD(&help->expectations); in nf_ct_helper_ext_add()
|
D | nf_conntrack_sip.c | 806 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()
|
D | nf_conntrack_core.c | 1618 if (ct->master || (help && !hlist_empty(&help->expectations))) in nf_conntrack_alter_reply()
|
D | nf_conntrack_netlink.c | 2905 hlist_for_each_entry_rcu(exp, &help->expectations, lnode) { in ctnetlink_exp_ct_dump_table()
|
/Linux-v4.19/drivers/fsi/ |
D | Kconfig | 25 to match old userspace expectations.
|
/Linux-v4.19/Documentation/devicetree/bindings/soc/qcom/ |
D | qcom,glink.txt | 53 meet expectations of the remote.
|
/Linux-v4.19/Documentation/driver-model/ |
D | device.txt | 97 strict expectations on when attributes get created. When a new device is
|
/Linux-v4.19/Documentation/filesystems/ |
D | dnotify.txt | 38 Implementation expectations (features and bugs :-))
|
/Linux-v4.19/Documentation/acpi/apei/ |
D | einj.txt | 152 creativity in using this feature expands beyond our expectations).
|
/Linux-v4.19/Documentation/laptops/ |
D | disk-shock-protection.txt | 74 milliseconds may raise expectations that cannot be satisfied in
|
/Linux-v4.19/Documentation/power/ |
D | pm_qos_interface.txt | 4 performance expectations by drivers, subsystems and user space applications on
|
/Linux-v4.19/Documentation/arm64/ |
D | acpi_object_usage.txt | 3 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
|
D | arm-acpi.txt | 484 Detailed expectations for ACPI tables and object are listed in the file
|
/Linux-v4.19/Documentation/ioctl/ |
D | botching-up-ioctls.txt | 99 Check that the error code matches your expectations. And finally make sure
|
/Linux-v4.19/Documentation/core-api/ |
D | atomic_ops.rst | 572 Spinlocks and rwlocks have memory barrier expectations as well.
|
/Linux-v4.19/Documentation/x86/ |
D | boot.txt | 8 expectations in the PC industry caused by the effective demise of
|
/Linux-v4.19/Documentation/block/ |
D | biodoc.txt | 379 The following were some of the goals and expectations considered in the
|