Home
last modified time | relevance | path

Searched full:followed (Results 1 – 25 of 1211) sorted by relevance

12345678910>>...49

/Linux-v6.1/tools/include/uapi/linux/
Dbtf.h86 * followed by extra data.
89 /* BTF_KIND_INT is followed by a u32 and the following
101 /* BTF_KIND_ENUM is followed by multiple "struct btf_enum".
110 /* BTF_KIND_ARRAY is followed by one "struct btf_array" */
117 /* BTF_KIND_STRUCT and BTF_KIND_UNION are followed
141 /* BTF_KIND_FUNC_PROTO is followed by multiple "struct btf_param".
162 /* BTF_KIND_VAR is followed by a single "struct btf_var" to describe
169 /* BTF_KIND_DATASEC is followed by multiple "struct btf_var_secinfo"
179 /* BTF_KIND_DECL_TAG is followed by a single "struct btf_decl_tag" to describe
190 /* BTF_KIND_ENUM64 is followed by multiple "struct btf_enum64".
/Linux-v6.1/include/uapi/linux/
Dbtf.h86 * followed by extra data.
89 /* BTF_KIND_INT is followed by a u32 and the following
101 /* BTF_KIND_ENUM is followed by multiple "struct btf_enum".
110 /* BTF_KIND_ARRAY is followed by one "struct btf_array" */
117 /* BTF_KIND_STRUCT and BTF_KIND_UNION are followed
141 /* BTF_KIND_FUNC_PROTO is followed by multiple "struct btf_param".
162 /* BTF_KIND_VAR is followed by a single "struct btf_var" to describe
169 /* BTF_KIND_DATASEC is followed by multiple "struct btf_var_secinfo"
179 /* BTF_KIND_DECL_TAG is followed by a single "struct btf_decl_tag" to describe
190 /* BTF_KIND_ENUM64 is followed by multiple "struct btf_enum64".
Ddns_resolver.h80 * Header at the beginning of a V1 server list. This is followed directly by
92 * Header at the beginning of each V1 server record. This is followed by the
93 * characters of the name with no NUL-terminator, followed by the address
109 * Header at the beginning of each V1 address record. This is followed by the
Dvirtio_scsi.h43 /* SCSI command request, followed by data-out */
53 /* SCSI command request, followed by protection information */
65 /* Response, followed by sense data and data-in */
Di2c.h61 * START. That is followed by the slave address, and a bit encoding read
65 * group, it is followed by a STOP. Otherwise it is followed by the next
/Linux-v6.1/arch/arm/boot/dts/
Dexynos5420-cpus.dtsi65 #cooling-cells = <2>; /* min followed by max */
77 #cooling-cells = <2>; /* min followed by max */
89 #cooling-cells = <2>; /* min followed by max */
101 #cooling-cells = <2>; /* min followed by max */
113 #cooling-cells = <2>; /* min followed by max */
125 #cooling-cells = <2>; /* min followed by max */
137 #cooling-cells = <2>; /* min followed by max */
149 #cooling-cells = <2>; /* min followed by max */
Dexynos5422-cpus.dtsi64 #cooling-cells = <2>; /* min followed by max */
77 #cooling-cells = <2>; /* min followed by max */
90 #cooling-cells = <2>; /* min followed by max */
103 #cooling-cells = <2>; /* min followed by max */
116 #cooling-cells = <2>; /* min followed by max */
129 #cooling-cells = <2>; /* min followed by max */
142 #cooling-cells = <2>; /* min followed by max */
155 #cooling-cells = <2>; /* min followed by max */
/Linux-v6.1/Documentation/devicetree/bindings/soundwire/
Dqcom,sdw.txt68 data port. Out ports followed by In ports.
77 data port. Out ports followed by In ports.
86 Out ports followed by In ports. Used for Sample Interval
106 Out ports followed by In ports.
116 Out ports followed by In ports.
126 Out ports followed by In ports.
137 Out ports followed by In ports.
148 Out ports followed by In ports.
160 Out ports followed by In ports.
/Linux-v6.1/drivers/net/wireless/intersil/hostap/
Dhostap_80211.h21 /* possibly followed by Challenge text */
30 /* followed by SSID and Supported rates */
37 /* followed by Supported rates */
44 /* followed by SSID and Supported rates */
56 /* followed by some of SSID, Supported rates,
/Linux-v6.1/Documentation/devicetree/bindings/spi/
Dspi-fsl-dspi.txt7 "fsl,ls1012a-dspi" (optionally followed by "fsl,ls1021a-v1.0-dspi"),
9 "fsl,ls1043a-dspi" (optionally followed by "fsl,ls1021a-v1.0-dspi"),
10 "fsl,ls1046a-dspi" (optionally followed by "fsl,ls1021a-v1.0-dspi"),
11 "fsl,ls1088a-dspi" (optionally followed by "fsl,ls1021a-v1.0-dspi"),
12 "fsl,ls2080a-dspi" (optionally followed by "fsl,ls2085a-dspi"),
/Linux-v6.1/Documentation/staging/
Dlzo.rst142 Always followed by exactly one byte : H H H H H H H H
152 Always followed by exactly one byte : H H H H H H H H
158 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
169 In this case, it is followed by a fourth byte, X.
175 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
183 Always followed by exactly one byte : H H H H H H H H
190 Always followed by exactly one byte : H H H H H H H H
/Linux-v6.1/drivers/staging/ks7010/
Deap_packet.h17 /* followed by length octets of data */
26 /* followed by length octets of data */
51 /* followed by key_data_length bytes of key_data */
/Linux-v6.1/kernel/trace/
Dtrace_dynevent.c280 * appended to the current cmd string, followed by a separator, if
321 * followed by a separator, if applicable. This can be used to add
325 * followed by an operator, if applicable, followed by the rhs string,
326 * followed finally by a separator, if applicable. Before the
448 * whitespace, all followed by a separator, if applicable. After the
450 * the optional @operator is appended, followed by the second arg and
/Linux-v6.1/Documentation/driver-api/surface_aggregator/
Dssh.rst73 Each frame structure is followed by a CRC over this structure. The CRC over
75 after the frame structure and before the payload. The payload is followed by
96 A message consists of |SYN|, followed by the frame (|TYPE|, |LEN|, |SEQ| and
98 followed finally, regardless if the payload is present, the payload CRC. The
139 Each exchange begins with |SYN|, followed by a |DATA_SEQ|- or
140 |DATA_NSQ|-type frame, followed by its CRC, payload, and payload CRC. In
200 consists of an eight-byte command structure, followed by optional and
335 followed by a repetition of ``SEQ=0`` will not detect the second ``SEQ=0``
/Linux-v6.1/arch/powerpc/platforms/cell/spufs/
Dspu_restore.c198 * followed by stop-and-signal instruction after in restore_complete()
206 /* SPU_Status[P,H]=1. Add 'heq $0, $0' followed in restore_complete()
216 * followed by 'br -4' after end of restore in restore_complete()
226 * followed by 'br -4' after end of restore code. in restore_complete()
234 /* SPU_Status[I]=1. Add illegal instruction followed in restore_complete()
/Linux-v6.1/Documentation/driver-api/media/
Drc-core.rst44 given remote controller), followed by 8 bits of code. A bit "1" is modulated
45 with 560µs *PULSE* followed by 1690µs *SPACE* and a bit "0" is modulated
46 with 560µs *PULSE* followed by 560µs *SPACE*.
/Linux-v6.1/Documentation/firmware-guide/acpi/dsd/
Dleds.rst30 entry shall contain the string "led@" followed by the number of the LED,
31 followed by the referred object name. That object shall be named "LED" followed
/Linux-v6.1/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt48 of a string which is a command to be executed, followed by 1 or
69 of a string which is a command to be executed, followed by 1 or
89 individual command into a list, with the command being first, followed by all
/Linux-v6.1/scripts/kconfig/tests/preprocess/escape/
DKconfig15 # Unlike Make, '$' has special meaning only when it is followed by '('.
22 # You need a trick to escape '$' followed by '('
/Linux-v6.1/Documentation/devicetree/bindings/fpga/
Dxilinx-pr-decoupler.txt24 - compatible : Should contain "xlnx,pr-decoupler-1.00" followed by
26 "xlnx,dfx-axi-shutdown-manager-1.00" followed by
/Linux-v6.1/Documentation/admin-guide/LSM/
Dindex.rst21 followed by any number of "minor" modules and at most one "major" module.
29 be first, followed by any "minor" modules (e.g. Yama) and then
/Linux-v6.1/tools/perf/Documentation/
Djitdump-specification.txt29 …der is followed by a series of records, each starting with a fixed size header describing the type…
53 The file header is immediately followed by records. Each record starts with a fixed size header des…
161 …data[n]: an array of unwinding data, consisting of the EH Frame Header, followed by the actual EH …
Ditrace.txt57 The 'e' option may be followed by flags which affect what errors will or
63 If supported, the 'd' option may be followed by flags which affect what
/Linux-v6.1/Documentation/devicetree/bindings/board/
Dfsl-board.txt25 - compatible: should be a board-specific string followed by a string
56 - compatible: Should be a board-specific string followed by a string
/Linux-v6.1/tools/lib/bpf/
Dlibbpf_common.h53 * This dance with uninitialized declaration, followed by memset to zero,
54 * followed by assignment using compound literal syntax is done to preserve

12345678910>>...49