Searched full:string (Results 1 – 25 of 782) sorted by relevance
12345678910>>...32
| /Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 12 severity: <integer>, <severity string>
13 section: <integer>, severity: <integer>, <severity string>
16 fru_id: <uuid string>
17 fru_text: <string>
18 section_type: <section type string>
21 <severity string>* := recoverable | fatal | corrected | info
27 <section type string> := generic processor error | memory error | \
28 PCIe error | unknown, <uuid string>
35 [processor_type: <integer>, <proc type string>]
36 [processor_isa: <integer>, <proc isa string>]
[all …]
|
| /Documentation/netlink/ |
| D | genetlink-legacy.yaml | 13 type: [ string, integer ]
26 type: string
28 type: string
38 type: string
42 type: string
45 type: string
67 type: string
70 type: string
74 type: string
78 type: [ string, integer ]
[all …]
|
| D | genetlink-c.yaml | 13 type: [ string, integer ]
26 type: string
28 type: string
38 type: string
42 type: string
45 type: string
60 type: string
63 type: string
67 type: string
71 type: [ string, integer ]
[all …]
|
| D | netlink-raw.yaml | 13 type: [ string, integer ]
26 type: string
28 type: string
39 type: string
43 type: string
46 type: string
68 type: string
71 type: string
75 type: string
79 type: [ string, integer ]
[all …]
|
| D | genetlink.yaml | 13 type: [ string, integer ]
26 type: string
28 type: string
38 type: string
49 type: string
52 type: string
56 type: string
60 type: [ string, integer ]
64 type: [ string, integer ]
70 - type: string
[all …]
|
| /Documentation/pcmcia/ |
| D | devicetable.rst | 18 hashes of the string to the macro, e.g. if you want to match the product ID
19 string 1, you need to use
27 "modalias" in the sysfs directory of the PCMCIA device. It generates a string
31 The hex value after "pa" is the hash of product ID string 1, after "pb" for
32 string 2 and so on.
35 to determine the crc32 hash. Simply pass the string you want to evaluate
|
| /Documentation/filesystems/nfs/ |
| D | client-identifier.rst | 54 - co_ownerid: An arbitrary but fixed string.
70 "co_ownerid" string has several important properties:
72 - The "co_ownerid" string identifies the client during reboot
73 recovery, therefore the string is persistent across client
75 - The "co_ownerid" string helps servers distinguish the client
76 from others, therefore the string is globally unique. Note
80 "co_ownerid" string does not reveal private information about
82 - The content of the "co_ownerid" string is set and unchanging
85 "co_ownerid" string.
95 If distinct clients present the same "co_ownerid" string and use
[all …]
|
| /Documentation/devicetree/bindings/ptp/ |
| D | brcm,ptp-dte.txt | 4 - compatible: should contain the core compatibility string
5 and the SoC compatibility string. The SoC
6 compatibility string is to handle SoC specific
8 Core compatibility string:
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 1 DT compatible string versioning for SiFive open-source IP blocks
18 the suffixed number in the compatible string whenever the software
22 Driver developers can use compatible string "match" values such as
29 continue to specify an SoC-specific compatible string value, such as
32 or other system software can match on this string to apply them. The
33 IP block-specific compatible string (such as "sifive,uart0") should
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | max8925-backlight.txt | 4 - maxim,max8925-dual-string: whether support dual string
9 maxim,max8925-dual-string = <0>;
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-firewire | 17 Hexadecimal string representation of an u64.
33 and version are hexadecimal string representations of
69 Decimal string representation.
87 Hexadecimal string representation of an u24.
93 Hexadecimal string representation of an u24.
99 Hexadecimal string representation of an u24.
103 Hexadecimal string representation of an u24.
110 Hexadecimal string representation of an u24.
128 Colon-separated hexadecimal string representations of
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-client.rst | 26 string. File open and lock state shared between one client and one server
28 and transparent state migration, this identity string must not change
31 Without any other intervention, the Linux client uses a string that contains
36 work well as part of an nfs_client_id4 string.
38 The nfs.nfs4_unique_id boot parameter specifies a unique string that can be
43 The nfs.nfs4_unique_id string is typically a UUID, though it can contain
45 nfs4_unique_id string should be chosen when a client system is installed,
49 The string should remain fixed for the lifetime of the client. It can be
53 This string can be stored in an NFS client's grub.conf, or it can be provided
57 This uniquifier string will be the same for all NFS clients running in
[all …]
|
| /Documentation/bpf/ |
| D | prog_cgroup_sysctl.rst | 67 * ``bpf_sysctl_get_current_value()`` to get string value currently held by
71 * ``bpf_sysctl_get_new_value()`` to get new string value currently being
75 * ``bpf_sysctl_set_new_value()`` to override new string value currently being
80 string value set by the helper is treated and verified by kernel same way as
81 an equivalent string passed by user space.
84 i.e. as a string. Since many sysctl values represent an integer or a vector
86 string:
88 * ``bpf_strtol()`` to convert initial part of the string to long integer
90 * ``bpf_strtoul()`` to convert initial part of the string to unsigned long
99 sysctl name and value, parses string value to get vector of integers and uses
|
| /Documentation/devicetree/bindings/phy/ |
| D | nvidia,tegra194-xusb-padctl.yaml | 116 $ref: /schemas/types.yaml#/definitions/string
128 $ref: /schemas/types.yaml#/definitions/string
140 $ref: /schemas/types.yaml#/definitions/string
152 $ref: /schemas/types.yaml#/definitions/string
172 $ref: /schemas/types.yaml#/definitions/string
184 $ref: /schemas/types.yaml#/definitions/string
196 $ref: /schemas/types.yaml#/definitions/string
208 $ref: /schemas/types.yaml#/definitions/string
234 description: A string that determines the mode in which to
236 $ref: /schemas/types.yaml#/definitions/string
[all …]
|
| D | qcom,usb-8x16-phy.txt | 5 Value type: <string>
22 Value type: <string>
47 Value type: <string>
48 Definition: Must contain "phy" string.
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-intel-m10-bmc-sec-update | 7 string: "hash not programmed". This file is only
9 Format: string.
17 returns the string: "hash not programmed". This file
19 Format: string.
26 if one is programmed, else it returns the string:
29 Format: string.
|
| D | sysfs-driver-input-exc3000 | 8 Valid values: Represented as string
17 Valid values: Represented as string
26 Valid values: Represented as string
|
| D | sysfs-class-fc | 16 The interface expects a string "<cgroupid>:<appid>" where:
18 <appid> is user provided string upto 128 characters
27 following string: "<cgroupid>:"
|
| D | sysfs-platform-wilco-ec | 16 Output will a MM/DD/YY string.
23 Output will a version string be similar to the example below:
31 Output will a version string be similar to the example below:
57 The format of the string is x.y.z. Where x is major, y is minor
|
| /Documentation/devicetree/bindings/board/ |
| D | fsl-board.txt | 25 - compatible: should be a board-specific string followed by a string
56 - compatible: Should be a board-specific string followed by a string
72 - compatible: Should be a board-specific string like "fsl,<board>-cpld"
|
| /Documentation/devicetree/bindings/sound/ |
| D | component-common.yaml | 14 $ref: /schemas/types.yaml#/definitions/string
17 audio components as list of string pair. Component using the same
19 sinks/sources with the provided string.
|
| /Documentation/trace/ |
| D | kprobetrace.rst | 61 (x8/x16/x32/x64), "char", "string", "ustring", "symbol", "symstr"
89 String type is a special type, which fetches a "null-terminated" string from
90 kernel space. This means it will fail and store NULL if the string container
91 has been paged out. "ustring" type is an alternative of string for user-space.
94 The string array type is a bit different from other types. For other base
96 as +0(%di):x32.) But string[1] is not equal to string. The string type itself
97 represents "char array", but string array type represents "char * array".
98 So, for example, +0(%di):string[1] is equal to +0(+0(%di)):string.
106 On the other hand, symbol-string type ('symstr') converts the given address to
107 "symbol+offset/symbolsize" style and stores it as a null-terminated string.
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-uevent.rst | 26 :Type: string
33 :Type: string
49 :Type: string
64 :Type: string
71 :Type: string
73 :Value: UUID. (Empty string if there isn't one.)
|
| /Documentation/devicetree/bindings/usb/ |
| D | aspeed,usb-vhub.yaml | 80 '^string@[0-9a-f]+$':
83 description: string descriptors of the specific language
92 $ref: /schemas/types.yaml#/definitions/string
96 $ref: /schemas/types.yaml#/definitions/string
100 $ref: /schemas/types.yaml#/definitions/string
132 string@409 {
|
| /Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 26 - format string
112 match-spec ::= 'func' string |
113 'file' string |
114 'module' string |
115 'format' string |
116 'class' string |
135 The given string is compared against the function name
142 The given string is compared against either the src-root relative
153 The given string is compared against the module name
154 of each callsite. The module name is the string as
[all …]
|
12345678910>>...32