Home
last modified time | relevance | path

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

12345678910>>...38

/linux/tools/include/uapi/linux/
H A Dbtf.h99 * followed by extra data.
102 /* BTF_KIND_INT is followed by a u32 and the following
114 /* BTF_KIND_ENUM is followed by multiple "struct btf_enum".
123 /* BTF_KIND_ARRAY is followed by one "struct btf_array" */
130 /* BTF_KIND_STRUCT and BTF_KIND_UNION are followed
154 /* BTF_KIND_FUNC_PROTO is followed by multiple "struct btf_param".
175 /* BTF_KIND_VAR is followed by a single "struct btf_var" to describe
182 /* BTF_KIND_DATASEC is followed by multiple "struct btf_var_secinfo"
192 /* BTF_KIND_DECL_TAG is followed by a single "struct btf_decl_tag" to describe
203 /* BTF_KIND_ENUM64 is followed b
[all...]
/linux/arch/arm/boot/dts/samsung/
H A 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 */
H A 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 */
H A Dexynos4412.dtsi50 #cooling-cells = <2>; /* min followed by max */
60 #cooling-cells = <2>; /* min followed by max */
70 #cooling-cells = <2>; /* min followed by max */
80 #cooling-cells = <2>; /* min followed by max */
/linux/Documentation/staging/
H A 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/include/uapi/linux/
H A 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
H A 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 */
H A Di2c.h62 * START. That is followed by the slave address, and a bit encoding read
66 * group, it is followed by a STOP. Otherwise it is followed by the next
/linux/Documentation/litmus-tests/
H A DREADME16 Test that an atomic RMW followed by a smp_mb__after_atomic() is
26 when followed by smp_mb__after_atomic().
30 operation when followed by smp_mb__after_atomic().
/linux/kernel/trace/
H A Dtrace_dynevent.c296 * appended to the current cmd string, followed by a separator, if
337 * followed by a separator, if applicable. This can be used to add
341 * followed by an operator, if applicable, followed by the rhs string,
342 * followed finally by a separator, if applicable. Before the
464 * whitespace, all followed by a separator, if applicable. After the
466 * the optional @operator is appended, followed by the second arg and
/linux/Documentation/driver-api/surface_aggregator/
H A Dssh.rst74 Each frame structure is followed by a CRC over this structure. The CRC over
76 after the frame structure and before the payload. The payload is followed by
97 A message consists of |SYN|, followed by the frame (|TYPE|, |LEN|, |SEQ| and
99 followed finally, regardless if the payload is present, the payload CRC. The
140 Each exchange begins with |SYN|, followed by a |DATA_SEQ|- or
141 |DATA_NSQ|-type frame, followed by its CRC, payload, and payload CRC. In
201 consists of an eight-byte command structure, followed by optional and
337 followed by a repetition of ``SEQ=0`` will not detect the second ``SEQ=0``
/linux/arch/powerpc/platforms/cell/spufs/
H A 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/Documentation/firmware-guide/acpi/dsd/
H A Dleds.rst25 entry shall contain the string "led@" followed by the number of the LED,
26 followed by the referred object name. That object shall be named "LED" followed
H A Dgraph.rst45 with "port" and must be followed by the "@" character and the number of the
53 "endpoint" and must be followed by the "@" character and the number of the
69 name followed by a string reference in the same package. [data-node-ref]::
/linux/Documentation/driver-api/media/
H A 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/tools/testing/selftests/tc-testing/creating-testcases/
H A DAddingTestCases.txt50 of a string which is a command to be executed, followed by 1 or
71 of a string which is a command to be executed, followed by 1 or
91 individual command into a list, with the command being first, followed by all
/linux/scripts/kconfig/tests/preprocess/escape/
H A DKconfig15 # Unlike Make, '$' has special meaning only when it is followed by '('.
22 # You need a trick to escape '$' followed by '('
/linux/tools/perf/Documentation/
H A 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 …
/linux/include/linux/
H A Dkthread.h66 * Description: Convenient wrapper for kthread_create() followed by
87 * followed by wake_up_process(). Returns the kthread or
223 * Description: Convenient wrapper for kthread_create_worker() followed by
247 * followed by wake_up_process(). Returns the kthread_worker or
/linux/security/apparmor/include/
H A Dpolicy_unpack.h54 * The AppArmor interface treats data as a type byte followed by the
56 * which has a name (AA_NAME typecode followed by name string) followed by
/linux/drivers/gpu/drm/imagination/
H A Dpvr_rogue_fwif_stream.h25 * current GPU. This stream is comprised of one or more headers, followed by data for each given
30 * continuation bit determining whether any more headers are present. The headers are then followed
/linux/tools/memory-model/litmus-tests/
H A DREADME11 from a given variable followed by a write to that same variable
16 to a given variable followed by a read from that same variable
75 in one process, and use an acquire load followed by a pair of
80 acquire load followed by a pair of spin_is_locked() calls
/linux/drivers/hid/
H A Dhid-appleir.c71 * 25 87 ee 91 5f followed by
74 * 25 87 ee 91 5c followed by
80 * 25 87 ee a3 5e followed by
83 * 25 87 ee a3 5d followed by
/linux/tools/testing/selftests/powerpc/vphn/
H A Dtest-vphn.c246 "vphn: 16-bit value followed by 32-bit value",
262 "vphn: 32-bit value followed by 16-bit value",
281 "vphn: 16-bit value followed by 2 x 32-bit values",
/linux/Documentation/networking/
H A Dmptcp.rst134 - ``MPTCP_TCPINFO``: Uses ``struct mptcp_subflow_data``, followed by an array of
136 - ``MPTCP_SUBFLOW_ADDRS``: Uses ``struct mptcp_subflow_data``, followed by an
141 ``struct tcp_info``, followed by the content of ``struct mptcp_info``.

12345678910>>...38