Searched full:descriptive (Results 1 – 25 of 33) sorted by relevance
12
| /Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 27 Try to give error codes names that are as reasonably descriptive of the error
30 descriptive and useful error messages.
|
| D | CodingStyle.rst | 185 organized into small clean and tidy modules, with clear and descriptive names
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | hwmon-common.yaml | 14 description: A descriptive name for this device.
|
| D | ti,tmp421.yaml | 55 A descriptive name for this channel, like "ambient" or "psu".
|
| D | ti,tmp464.yaml | 54 A descriptive name for this channel, like "ambient" or "psu".
|
| D | national,lm90.yaml | 84 description: A descriptive name for this channel, like "ambient" or "psu".
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | panel-common.yaml | 23 # Descriptive Properties
43 non-descriptive information. For instance an LCD panel in a system that
45 inscribed on the system or used in a descriptive fashion in system
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-pca9570.yaml | 32 description: A descriptive name for this device.
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 28 /label ... (r/o) descriptive, not necessarily unique
|
| /Documentation/devicetree/bindings/input/ |
| D | matrix-keymap.yaml | 19 for said properties are "linux,fn-keymap" or with another descriptive
|
| D | allwinner,sun4i-a10-lradc-keys.yaml | 54 description: Descriptive name of the key
|
| D | gpio-keys.yaml | 53 description: Descriptive name of the key.
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-cadence.yaml | 56 description: Descriptive name of the SPI controller.
|
| /Documentation/power/regulator/ |
| D | machine.rst | 52 The name field should be set to something that is usefully descriptive
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl-tsec-phy.txt | 43 is considered instructive, rather than descriptive. The reg property should
|
| /Documentation/input/ |
| D | userio.rst | 49 returned by the character device and a more descriptive error will be printed
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 68 to give each blob a descriptive name. For example::
|
| /Documentation/sound/cards/ |
| D | pcmtest.rst | 68 The driver has 'inject_delay' parameter, which has very self-descriptive name and
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | at24.yaml | 147 description: Descriptive name of the EEPROM.
|
| /Documentation/doc-guide/ |
| D | kernel-doc.rst | 150 #) The multi-line descriptive text you provide does *not* recognize
169 #) If the descriptive text you provide has lines that begin with
393 descriptive text and converted to proper reStructuredText markup and `Sphinx C
|
| /Documentation/userspace-api/gpio/ |
| D | sysfs.rst | 171 a descriptive name.
|
| /Documentation/trace/ |
| D | mmiotrace.rst | 73 which action. It is recommended to place descriptive markers about what you
|
| /Documentation/process/ |
| D | maintainer-tip.rst | 597 usage of descriptive function names often replaces these tiny comments.
721 Either use proper defines which have descriptive names or consider using
824 can have shorter descriptive names - our primary concern is greppability
|
| D | coding-style.rst | 315 HOWEVER, while mixed-case names are frowned upon, descriptive names for
320 have descriptive names, as do global functions. If you have a function
460 descriptive names (you can ask the compiler to in-line them if you think
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 15 description: A string used as a descriptive name for regulator outputs
|
12