| /Linux-v4.19/fs/exportfs/ |
| D | expfs.c | 43 int (*acceptable)(void *context, struct dentry *dentry), in find_acceptable_alias()
49 if (acceptable(context, result)) in find_acceptable_alias()
59 if (dentry != result && acceptable(context, dentry)) { in find_acceptable_alias()
420 int (*acceptable)(void *, struct dentry *), void *context) in exportfs_decode_fh()
444 if (!acceptable) in exportfs_decode_fh()
462 if (!acceptable(context, result)) { in exportfs_decode_fh()
483 alias = find_acceptable_alias(result, acceptable, context); in exportfs_decode_fh()
544 alias = find_acceptable_alias(result, acceptable, context); in exportfs_decode_fh()
|
| /Linux-v4.19/Documentation/media/uapi/dvb/ |
| D | fe_property_parameters.rst | 159 The acceptable values are defined by :c:type:`fe_spectral_inversion`.
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`.
716 The acceptable values are defined by :c:type:`atscmh_rs_frame_mode`.
728 The acceptable values are defined by :c:type:`atscmh_rs_frame_ensemble`.
740 The acceptable values are defined by :c:type:`atscmh_rs_code_mode`.
752 The acceptable values are defined by :c:type:`atscmh_rs_code_mode`.
[all …]
|
| /Linux-v4.19/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 44 more acceptable exit codes for this command.
58 of 0 is acceptable.
65 more acceptable exit codes for this command.
82 It's possible to include acceptable exit codes with the setup/teardown command
85 acceptable exit codes for the command.
|
| /Linux-v4.19/drivers/pci/pcie/ |
| D | aspm.c | 78 struct aspm_latency acceptable[8]; member
421 struct aspm_latency *acceptable; in pcie_aspm_check_latency() local
430 acceptable = &link->acceptable[PCI_FUNC(endpoint->devfn)]; in pcie_aspm_check_latency()
435 (link->latency_up.l0s > acceptable->l0s)) in pcie_aspm_check_latency()
440 (link->latency_dw.l0s > acceptable->l0s)) in pcie_aspm_check_latency()
457 (latency + l1_switch_latency > acceptable->l1)) in pcie_aspm_check_latency()
628 struct aspm_latency *acceptable = in pcie_aspm_cap_init() local
629 &link->acceptable[PCI_FUNC(child->devfn)]; in pcie_aspm_cap_init()
638 acceptable->l0s = calc_l0s_acceptable(encoding); in pcie_aspm_cap_init()
641 acceptable->l1 = calc_l1_acceptable(encoding); in pcie_aspm_cap_init()
|
| /Linux-v4.19/net/dccp/ |
| D | input.c | 581 bool acceptable; in dccp_rcv_state_process() local
613 acceptable = inet_csk(sk)->icsk_af_ops->conn_request(sk, skb) >= 0; in dccp_rcv_state_process()
616 if (!acceptable) in dccp_rcv_state_process()
|
| /Linux-v4.19/include/linux/ |
| D | exportfs.h | 218 int fh_len, int fileid_type, int (*acceptable)(void *, struct dentry *),
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/ |
| D | socionext,uniphier-ave4.txt | 17 The acceptable mode is SoC-dependent.
|
| /Linux-v4.19/Documentation/networking/ |
| D | dccp.txt | 114 range 0..15 are acceptable. The default setting is 0 (full coverage),
117 sets a threshold, where again values 0..15 are acceptable. The default
120 coverage value are also acceptable. The higher the number, the more
|
| D | nf_conntrack-sysctl.txt | 117 received an (acceptable) ACK from the destination. If this number
|
| D | tproxy.txt | 59 acceptable in certain situations. (Think of proxying UDP for example: you won't
|
| /Linux-v4.19/Documentation/ |
| D | pnp.txt | 80 Dependent: 01 - Priority acceptable
85 Dependent: 02 - Priority acceptable
|
| /Linux-v4.19/Documentation/process/ |
| D | code-of-conduct.rst | 44 Maintainers are responsible for clarifying the standards of acceptable behavior
|
| /Linux-v4.19/Documentation/power/regulator/ |
| D | consumer.txt | 79 Where min_uV and max_uV are the minimum and maximum acceptable voltages in
109 Where min_uA and max_uA are the minimum and maximum acceptable current limit in
|
| /Linux-v4.19/Documentation/scsi/ |
| D | megaraid.txt | 31 "Shared code in a third module, a "library module", is an acceptable
|
| /Linux-v4.19/Documentation/arm64/ |
| D | silicon-errata.txt | 13 Category B: A significant or critical error with an acceptable
|
| /Linux-v4.19/Documentation/acpi/ |
| D | linuxized-acpica.txt | 108 As the coding style adopted by the ACPICA project is not acceptable by
199 Those changes may not be acceptable by ACPICA upstream and in such cases
|
| /Linux-v4.19/Documentation/bpf/ |
| D | bpf_design_QA.rst | 135 workaround would be acceptable. Turned out that programs lose performance
138 instructions are acceptable and can be added in the future.
|
| /Linux-v4.19/Documentation/timers/ |
| D | timers-howto.txt | 91 be balanced with what is an acceptable upper bound on
|
| /Linux-v4.19/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 42 acceptable to allocate from.
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-g-fmt.rst | 66 parameters acceptable for both the application and driver. On success
|
| D | field-order.rst | 71 ``V4L2_FIELD_INTERLACED`` formats is acceptable. Drivers choose
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/ |
| D | coresight.txt | 66 * reg-names: the only acceptable values are "stm-base" and
|
| /Linux-v4.19/Documentation/arm/ |
| D | IXP4xx | 90 cases the performance hit is acceptable. In addition, you cannot
|
| /Linux-v4.19/Documentation/arm/nwfpe/ |
| D | README.FPE | 89 equivalent to the MUF/DVF/RDV instructions. This is acceptable according
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | submitting-patches | 95 and messages printed after a successful detection are acceptable, but it
|
