/linux-6.1.9/fs/exportfs/ |
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() 422 int (*acceptable)(void *, struct dentry *), in exportfs_decode_fh_raw() 445 if (!acceptable) in exportfs_decode_fh_raw() 463 if (!acceptable(context, result)) { in exportfs_decode_fh_raw() 484 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-6.1.9/Documentation/userspace-api/media/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-6.1.9/tools/testing/selftests/tc-testing/creating-testcases/ |
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-6.1.9/include/linux/ |
D | exportfs.h | 234 int (*acceptable)(void *, struct dentry *), 237 int fh_len, int fileid_type, int (*acceptable)(void *, struct dentry *),
|
/linux-6.1.9/net/dccp/ |
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-6.1.9/Documentation/networking/ |
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
|
D | tproxy.rst | 62 acceptable in certain situations. (Think of proxying UDP for example: you won't
|
D | nf_conntrack-sysctl.rst | 127 received an (acceptable) ACK from the destination. If this number
|
/linux-6.1.9/Documentation/admin-guide/ |
D | pnp.rst | 80 Dependent: 01 - Priority acceptable 85 Dependent: 02 - Priority acceptable
|
/linux-6.1.9/Documentation/devicetree/bindings/reserved-memory/ |
D | reserved-memory.yaml | 53 acceptable to allocate from.
|
/linux-6.1.9/Documentation/process/ |
D | code-of-conduct.rst | 44 Maintainers are responsible for clarifying the standards of acceptable behavior
|
D | researcher-guidelines.rst | 21 acceptable and non-acceptable practices when conducting such research. At
|
D | handling-regressions.rst | 194 found. Two or three additional weeks are acceptable for performance 198 total are acceptable if a regression can only be fixed with a risky change 211 it might even be acceptable to skip testing in linux-next. Especially fixes for 226 proposed change; if problems surface, maybe some solution acceptable for all 491 way", and I simply don't think that's acceptable outside of very early
|
/linux-6.1.9/Documentation/power/regulator/ |
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-6.1.9/Documentation/scsi/ |
D | megaraid.rst | 36 "Shared code in a third module, a "library module", is an acceptable
|
/linux-6.1.9/Documentation/driver-api/acpi/ |
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-6.1.9/Documentation/bpf/ |
D | prog_cgroup_sockopt.rst | 52 Note, that the only acceptable value to set to ``retval`` is 0 and the
|
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-6.1.9/Documentation/timers/ |
D | timers-howto.rst | 98 be balanced with what is an acceptable upper bound on
|
/linux-6.1.9/Documentation/arm64/ |
D | silicon-errata.rst | 16 Category B A significant or critical error with an acceptable
|
/linux-6.1.9/Documentation/ABI/stable/ |
D | sysfs-driver-dma-idxd | 289 the ENGCAP register. The acceptable values are 0 (default), 301 the ENGCAP register. The acceptable values are 0 (default),
|
/linux-6.1.9/lib/ |
D | Kconfig.ubsan | 27 the system. For some system builders this is an acceptable
|
/linux-6.1.9/Documentation/userspace-api/media/v4l/ |
D | vidioc-g-fmt.rst | 68 parameters acceptable for both the application and driver. On success
|
/linux-6.1.9/Documentation/core-api/ |
D | pin_user_pages.rst | 100 are acceptable, but false negatives are not. 111 And again, that's acceptable.
|
/linux-6.1.9/Documentation/arm/ |
D | ixp4xx.rst | 90 cases the performance hit is acceptable. In addition, you cannot
|