| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | dmx-mmap.rst | 34 address cannot be used. Use of this option is discouraged;
58 discouraged.
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | func-mmap.rst | 32 address cannot be used. Use of this option is discouraged;
73 discouraged.
|
| /openbmc/linux/tools/lib/bpf/ |
| H A D | libbpf_legacy.h | 4 * Libbpf legacy APIs (either discouraged or deprecated, as mentioned in [0])
117 /* "Discouraged" APIs which don't follow consistent libbpf naming patterns.
|
| /openbmc/linux/drivers/atm/ |
| H A D | Kconfig | 89 bool "Enable 16W TX bursts (discouraged)"
119 bool "Enable 16W RX bursts (discouraged)"
126 bool "Enable 8W RX bursts (discouraged)"
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-info.rst | 19 versions is generally discouraged - here, and via any other Linux API.
111 so adding API versions is generally discouraged as noise.
|
| /openbmc/linux/fs/smb/client/ |
| H A D | Kconfig | 37 older than SMB2.1 is often discouraged on public networks.
77 of legacy dialects (SMB1/CIFS and SMB2.0) is discouraged.
|
| /openbmc/linux/drivers/iommu/iommufd/ |
| H A D | Kconfig | 31 enabling of this option is currently discouraged.
|
| /openbmc/linux/tools/leds/ |
| H A D | get_led_device_info.sh | 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"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/ |
| H A D | README.md | 27 Note, it is discouraged to send patches via GitHub pull request system. Such
|
| /openbmc/webui-vue/docs/customization/ |
| H A D | theme.md | 149 files is discouraged to avoid tightly coupling the OpenBMC Web UI theme to
155 components is discouraged.
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio.txt | 161 indicating the usage. Package names, such as a pin name, are discouraged:
173 are strongly discouraged. For example "pin8 [gpio14/uart0_txd]" is fine
177 In either case placeholders are discouraged: rather use the "" (blank
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | example-schema.yaml | 84 discouraged.
104 discouraged.
|
| /openbmc/linux/arch/powerpc/include/asm/ |
| H A D | rtas-work-area.h | 42 * succeeds. To prevent deadlocks, callers are discouraged from
|
| /openbmc/qemu/include/crypto/ |
| H A D | tlscredsanon.h | 41 * its use is discouraged as it has poor security characteristics
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | redfish-schema.v1_10_0.json | |
| H A D | redfish-schema-v1.json | 33 "description": "The term shall be applied to a property in order to specify that the property is deprecated. The value of the string should explain the deprecation, including new property or properties to be used. The property can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated properties are likely to be removed in a future major version of the schema."
53 "description": "The term shall be applied to a value in order to specify that the value is deprecated. The value of the string should explain the deprecation, including new value to be used. The value can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated values are likely to be removed in a future major version of the schema."
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | redfish-schema.v1_10_0.json | |
| H A D | redfish-schema-v1.json | 33 "description": "The term shall be applied to a property in order to specify that the property is deprecated. The value of the string should explain the deprecation, including new property or properties to be used. The property can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated properties are likely to be removed in a future major version of the schema."
53 "description": "The term shall be applied to a value in order to specify that the value is deprecated. The value of the string should explain the deprecation, including new value to be used. The value can be supported in new and existing implementations, but usage in new implementations is discouraged. Deprecated values are likely to be removed in a future major version of the schema."
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | tagged-pointers.rst | 46 discouraged.
|
| /openbmc/linux/Documentation/devicetree/bindings/timer/ |
| H A D | arm,arch_timer_mmio.yaml | 41 strongly discouraged; fix your firmware unless absolutely impossible.
|
| H A D | arm,arch_timer.yaml | 64 strongly discouraged; fix your firmware unless absolutely impossible.
|
| /openbmc/linux/sound/pci/au88x0/ |
| H A D | au88x0_mpu401.c | 18 * for older versions of ALSA. Its usage is strongly discouraged. */
|
| /openbmc/linux/Documentation/timers/ |
| H A D | timers-howto.rst | 35 In general, use of mdelay is discouraged and code should
|
| /openbmc/linux/Documentation/devicetree/bindings/dma/ |
| H A D | snps,dma-spear1340.yaml | 106 deprecated. It' usage is discouraged in favor of data-width one. Moreover
|
| /openbmc/qemu/docs/interop/ |
| H A D | qmp-spec.rst | 413 discouraged.
437 4. New capabilities are strongly discouraged. Capabilities are for
|