Searched full:discouraged (Results 1 – 25 of 113) sorted by relevance
12345
34 address cannot be used. Use of this option is discouraged;58 discouraged.
33 address cannot be used. Use of this option is discouraged;57 discouraged.
34 address cannot be used. Use of this option is discouraged;75 discouraged.
32 address cannot be used. Use of this option is discouraged;73 discouraged.
19 versions is generally discouraged - here, and via any other Linux API.111 so adding API versions is generally discouraged as noise.
169 print_msg_failed "$S_DEV" "$devicename" "Redundant: use of vendor name is discouraged"171 print_msg_failed "$S_DEV" "$devicename" "Redundant: use of product name is discouraged"
89 bool "Enable 16W TX bursts (discouraged)"119 bool "Enable 16W RX bursts (discouraged)"126 bool "Enable 8W RX bursts (discouraged)"
32 dialects older than SMB2.1 is often discouraged on public networks.75 of legacy dialects (SMB1/CIFS and SMB2.0) is discouraged.
35 dialects older than SMB2.1 is often discouraged on public networks.78 of legacy dialects (SMB1/CIFS and SMB2.0) is discouraged.
85 discouraged.103 discouraged.
28 * The use of kmap_atomic/kunmap_atomic is discouraged - kmap/kunmap
40 strongly discouraged.
46 discouraged.
16 * The use of kmap_atomic/kunmap_atomic is discouraged - kmap/kunmap
41 strongly discouraged; fix your firmware unless absolutely impossible.
47 strongly discouraged; fix your firmware unless absolutely impossible.
18 * for older versions of ALSA. Its usage is strongly discouraged. */
124 nevertheless discouraged as the effective memory type is considered143 (*) denotes implementation defined and is discouraged
23 strongly discouraged; fix your firmware unless absolutely impossible.
34 In general, use of mdelay is discouraged and code should
35 In general, use of mdelay is discouraged and code should