Searched full:discouraged (Results 1 – 25 of 140) sorted by relevance
123456
34 address cannot be used. Use of this option is discouraged;58 discouraged.
32 address cannot be used. Use of this option is discouraged;73 discouraged.
4 * Libbpf legacy APIs (either discouraged or deprecated, as mentioned in [0])117 /* "Discouraged" APIs which don't follow consistent libbpf naming patterns.
89 bool "Enable 16W TX bursts (discouraged)"119 bool "Enable 16W RX bursts (discouraged)"126 bool "Enable 8W RX bursts (discouraged)"
19 versions is generally discouraged - here, and via any other Linux API.111 so adding API versions is generally discouraged as noise.
37 older than SMB2.1 is often discouraged on public networks.77 of legacy dialects (SMB1/CIFS and SMB2.0) is discouraged.
31 enabling of this option is currently discouraged.
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"
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
161 indicating the usage. Package names, such as a pin name, are discouraged:173 are strongly discouraged. For example "pin8 [gpio14/uart0_txd]" is fine177 In either case placeholders are discouraged: rather use the "" (blank
84 discouraged.104 discouraged.
42 * succeeds. To prevent deadlocks, callers are discouraged from
46 discouraged.
16 * The use of kmap_atomic/kunmap_atomic is discouraged - kmap/kunmap
47 strongly discouraged; fix your firmware unless absolutely impossible.
41 strongly discouraged; fix your firmware unless absolutely impossible.