| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe_property_parameters.rst | 164 The acceptable values are defined by :c:type:`fe_spectral_inversion`.
192 The acceptable values are defined by :c:type:`fe_code_rate`.
207 The acceptable values are defined by :c:type:`fe_sec_voltage`.
227 The acceptable values are defined by :c:type:`fe_pilot`.
239 The acceptable values are defined by :c:type:`fe_rolloff`.
273 The acceptable values are defined by :c:type:`fe_delivery_system`.
721 The acceptable values are defined by :c:type:`atscmh_rs_frame_mode`.
733 The acceptable values are defined by :c:type:`atscmh_rs_frame_ensemble`.
745 The acceptable values are defined by :c:type:`atscmh_rs_code_mode`.
757 The acceptable values are defined by :c:type:`atscmh_rs_code_mode`.
[all …]
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| H A D | AddingTestCases.txt | 51 more acceptable exit codes for this command.
65 of 0 is acceptable.
72 more acceptable exit codes for this command.
89 It's possible to include acceptable exit codes with the setup/teardown command
92 acceptable exit codes for the command.
|
| /linux/Documentation/networking/ |
| H A D | smc-sysctl.rst | 64 of RDMA devices exist in the system. The acceptable value ranges from 1 to 2. Only
71 acceptable value ranges from 16 to 255. Only for SMC-R v2.1 and later.
|
| H 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
|
| H A D | tproxy.rst | 62 acceptable in certain situations. (Think of proxying UDP for example: you won't
|
| H A D | nf_conntrack-sysctl.rst | 127 received an (acceptable) ACK from the destination. If this number
|
| /linux/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 202 It is the responsibility of userspace to negotiate an acceptable format+modifier
213 Vulkan, to obtain a final list of acceptable modifiers for that format
232 acceptable modifiers, it must allocate the buffer. As there is no universal
238 acceptable modifiers, and the buffer's width and height. Each API may extend
243 it considers the 'best' modifier within the acceptable list for the requested
253 provided within the acceptable list, nor to vary the pixel dimensions other than
315 list of acceptable modifiers that the implementation can choose from (or fail if
347 modifiers is acceptable
353 list of acceptable modifiers, or not provided a list
356 unknown for whatever reason; this is only acceptable when the buffer has
|
| /linux/net/dccp/ |
| H 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/ABI/testing/ |
| H A D | configfs-tsm | 84 privilege level via this attribute. The minimum acceptable
86 acceptable value is TSM_PRIVLEVEL_MAX (3).
|
| /linux/Documentation/admin-guide/ |
| H A D | pnp.rst | 80 Dependent: 01 - Priority acceptable
85 Dependent: 02 - Priority acceptable
|
| /linux/Documentation/power/regulator/ |
| H 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/ |
| H A D | code-of-conduct.rst | 44 Maintainers are responsible for clarifying the standards of acceptable behavior
|
| H A D | researcher-guidelines.rst | 21 acceptable and non-acceptable practices when conducting such research. At
|
| /linux/Documentation/scsi/ |
| H A D | megaraid.rst | 36 "Shared code in a third module, a "library module", is an acceptable
|
| /linux/Documentation/driver-api/acpi/ |
| H 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/tools/sched_ext/ |
| H A D | README.md | 13 production environment with acceptable or possibly even improved performance.
14 Others are just examples that in practice, would not provide acceptable
|
| /linux/Documentation/bpf/ |
| H A D | prog_cgroup_sockopt.rst | 52 Note, that the only acceptable value to set to ``retval`` is 0 and the
|
| H A D | bpf_design_QA.rst | 155 workaround would be acceptable. Turned out that programs lose performance
158 instructions are acceptable and can be added in the future.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-fmt.rst | 68 parameters acceptable for both the application and driver. On success
|
| H A D | field-order.rst | 77 is acceptable. Drivers choose depending on hardware capabilities or
|
| /linux/Documentation/rust/ |
| H A D | general-information.rst | 123 ``inline`` functions or non-trivial macros, it is acceptable to add a small
|
| /linux/Documentation/core-api/ |
| H A D | pin_user_pages.rst | 99 are acceptable, but false negatives are not.
110 And again, that's acceptable.
|
| /linux/lib/ |
| H A D | Kconfig.ubsan | 27 the system. For some system builders this is an acceptable
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | vdo.rst | 167 acceptable values are 'on' and 'off'.
171 acceptable values are 'on' and 'off'.
|
| /linux/Documentation/arch/arm/ |
| H A D | ixp4xx.rst | 90 cases the performance hit is acceptable. In addition, you cannot
|