Searched refs:expectations (Results 1 – 25 of 27) sorted by relevance
12
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | sysfs-acpi-pmprofile | 6 power management (and performance) requirement expectations
|
| /Linux-v5.4/drivers/soc/rockchip/ |
| D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /Linux-v5.4/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 | 5.Posting.rst | 11 document will attempt to cover these expectations in reasonable detail;
|
| D | 4.Coding.rst | 376 the expectations for new code are higher than they were in the past;
|
| /Linux-v5.4/include/net/netfilter/ |
| D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
| /Linux-v5.4/net/netfilter/ |
| D | nf_conntrack_expect.c | 223 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
388 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
404 hlist_for_each_entry(exp, &master_help->expectations, lnode) { in evict_oldest_expect()
|
| D | nf_conntrack_helper.c | 205 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()
|
| D | nf_conntrack_core.c | 1771 if (ct->master || (help && !hlist_empty(&help->expectations))) in nf_conntrack_alter_reply()
|
| D | nf_conntrack_netlink.c | 2954 hlist_for_each_entry_rcu(exp, &help->expectations, lnode) { in ctnetlink_exp_ct_dump_table()
|
| /Linux-v5.4/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,glink.txt | 58 meet expectations of the remote.
|
| /Linux-v5.4/drivers/fsi/ |
| D | Kconfig | 26 to match old userspace expectations.
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | device.rst | 100 strict expectations on when attributes get created. When a new device is
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | dnotify.txt | 38 Implementation expectations (features and bugs :-))
|
| /Linux-v5.4/Documentation/ |
| D | index.rst | 42 The following holds information on the kernel's expectations regarding the
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/apei/ |
| D | einj.rst | 160 creativity in using this feature expands beyond our expectations).
|
| /Linux-v5.4/Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 75 milliseconds may raise expectations that cannot be satisfied in
|
| /Linux-v5.4/Documentation/power/ |
| D | pm_qos_interface.rst | 6 performance expectations by drivers, subsystems and user space applications on
|
| /Linux-v5.4/Documentation/arm64/ |
| D | acpi_object_usage.rst | 5 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
|
| D | arm-acpi.rst | 487 Detailed expectations for ACPI tables and object are listed in the file
|
| /Linux-v5.4/Documentation/ioctl/ |
| D | botching-up-ioctls.rst | 100 Check that the error code matches your expectations. And finally make sure
|
| /Linux-v5.4/Documentation/core-api/ |
| D | atomic_ops.rst | 572 Spinlocks and rwlocks have memory barrier expectations as well.
|
12
