| /linux/fs/exportfs/ |
| A D | expfs.c | 44 int (*acceptable)(void *context, struct dentry *dentry), in find_acceptable_alias()
50 if (acceptable(context, result)) in find_acceptable_alias()
60 if (dentry != result && acceptable(context, dentry)) { in find_acceptable_alias()
423 int (*acceptable)(void *, struct dentry *), in exportfs_decode_fh_raw()
446 if (!acceptable) in exportfs_decode_fh_raw()
464 if (!acceptable(context, result)) { in exportfs_decode_fh_raw()
485 alias = find_acceptable_alias(result, acceptable, context); in exportfs_decode_fh_raw()
553 alias = find_acceptable_alias(result, acceptable, context); in exportfs_decode_fh_raw()
570 int (*acceptable)(void *, struct dentry *), in exportfs_decode_fh()
576 acceptable, context); in exportfs_decode_fh()
|
| /linux/Documentation/userspace-api/media/dvb/ |
| A D | fe_property_parameters.rst | 187 The acceptable values are defined by :c:type:`fe_code_rate`.
202 The acceptable values are defined by :c:type:`fe_sec_voltage`.
222 The acceptable values are defined by :c:type:`fe_pilot`.
234 The acceptable values are defined by :c:type:`fe_rolloff`.
268 The acceptable values are defined by :c:type:`fe_delivery_system`.
832 The acceptable values are defined by :c:type:`fe_transmit_mode`.
842 The acceptable values are defined by :c:type:`fe_transmit_mode`.
850 The acceptable values are defined by :c:type:`fe_guard_interval`.
876 The acceptable values are defined by :c:type:`fe_transmit_mode`.
911 The acceptable values are defined by :c:type:`fe_hierarchy`.
[all …]
|
| /linux/drivers/pci/pcie/ |
| A D | aspm.c | 76 struct aspm_latency acceptable[8]; member
382 struct aspm_latency *acceptable; in pcie_aspm_check_latency() local
391 acceptable = &link->acceptable[PCI_FUNC(endpoint->devfn)]; in pcie_aspm_check_latency()
396 (link->latency_up.l0s > acceptable->l0s)) in pcie_aspm_check_latency()
401 (link->latency_dw.l0s > acceptable->l0s)) in pcie_aspm_check_latency()
418 (latency + l1_switch_latency > acceptable->l1)) in pcie_aspm_check_latency()
664 struct aspm_latency *acceptable = in pcie_aspm_cap_init() local
665 &link->acceptable[PCI_FUNC(child->devfn)]; in pcie_aspm_cap_init()
674 acceptable->l0s = calc_l0s_acceptable(encoding); in pcie_aspm_cap_init()
677 acceptable->l1 = calc_l1_acceptable(encoding); in pcie_aspm_cap_init()
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| A D | AddingTestCases.txt | 49 more acceptable exit codes for this command.
63 of 0 is acceptable.
70 more acceptable exit codes for this command.
87 It's possible to include acceptable exit codes with the setup/teardown command
90 acceptable exit codes for the command.
|
| /linux/include/linux/ |
| A D | exportfs.h | 236 int (*acceptable)(void *, struct dentry *),
239 int fh_len, int fileid_type, int (*acceptable)(void *, struct dentry *),
|
| /linux/net/dccp/ |
| A D | input.c | 577 bool acceptable; in dccp_rcv_state_process() local
609 acceptable = inet_csk(sk)->icsk_af_ops->conn_request(sk, skb) >= 0; in dccp_rcv_state_process()
612 if (!acceptable) in dccp_rcv_state_process()
|
| /linux/Documentation/networking/ |
| A D | dccp.rst | 118 range 0..15 are acceptable. The default setting is 0 (full coverage),
122 sets a threshold, where again values 0..15 are acceptable. The default
125 coverage value are also acceptable. The higher the number, the more
|
| A D | tproxy.rst | 62 acceptable in certain situations. (Think of proxying UDP for example: you won't
|
| A D | nf_conntrack-sysctl.rst | 133 received an (acceptable) ACK from the destination. If this number
|
| /linux/Documentation/admin-guide/ |
| A D | pnp.rst | 80 Dependent: 01 - Priority acceptable
85 Dependent: 02 - Priority acceptable
|
| /linux/arch/arm/mach-ixp4xx/ |
| A D | Kconfig | 83 acceptable. In addition, you cannot mmap() PCI devices in this
|
| /linux/Documentation/devicetree/bindings/reserved-memory/ |
| A D | reserved-memory.yaml | 53 acceptable to allocate from.
|
| /linux/Documentation/power/regulator/ |
| A D | consumer.rst | 84 Where min_uV and max_uV are the minimum and maximum acceptable voltages in
115 Where min_uA and max_uA are the minimum and maximum acceptable current limit in
|
| /linux/Documentation/process/ |
| A D | code-of-conduct.rst | 44 Maintainers are responsible for clarifying the standards of acceptable behavior
|
| /linux/Documentation/scsi/ |
| A D | megaraid.rst | 36 "Shared code in a third module, a "library module", is an acceptable
|
| /linux/Documentation/driver-api/acpi/ |
| A D | linuxized-acpica.rst | 123 As the coding style adopted by the ACPICA project is not acceptable by
215 Those changes may not be acceptable by ACPICA upstream and in such cases
|
| /linux/Documentation/bpf/ |
| A D | prog_cgroup_sockopt.rst | 52 Note, that the only acceptable value to set to ``retval`` is 0 and the
|
| A D | bpf_design_QA.rst | 160 workaround would be acceptable. Turned out that programs lose performance
163 instructions are acceptable and can be added in the future.
|
| /linux/Documentation/timers/ |
| A D | timers-howto.rst | 98 be balanced with what is an acceptable upper bound on
|
| /linux/Documentation/arm64/ |
| A D | silicon-errata.rst | 16 Category B A significant or critical error with an acceptable
|
| /linux/Documentation/core-api/ |
| A D | pin_user_pages.rst | 100 are acceptable, but false negatives are not.
111 And again, that's acceptable.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| A D | vidioc-g-fmt.rst | 68 parameters acceptable for both the application and driver. On success
|
| A D | field-order.rst | 77 is acceptable. Drivers choose depending on hardware capabilities or
|
| /linux/lib/ |
| A D | Kconfig.ubsan | 27 the system. For some system builders this is an acceptable
|
| /linux/Documentation/arm/ |
| A D | ixp4xx.rst | 90 cases the performance hit is acceptable. In addition, you cannot
|