| /linux/Documentation/devicetree/bindings/scsi/ |
| H A D | hisilicon-sas.txt | 6 - compatible : value should be as follows:
22 sources; the interrupts are ordered in 3 groups, as follows:
35 Fatal interrupts : the fatal interrupts are ordered as follows:
39 the interrupts are ordered in 3 groups, as follows:
|
| /linux/Documentation/RCU/ |
| H A D | lockdep-splat.rst | 68 Line 2776 of block/cfq-iosched.c in v3.0-rc5 is as follows::
78 which would permit us to invoke rcu_dereference_protected as follows::
93 add rcu_read_lock() and rcu_read_unlock() as follows::
110 by rcu_access_pointer() as follows::
|
| H A D | rcuref.rst | 52 in this scenario as follows:
89 as follows:
140 delete(), so that el_free() can be subsumed into delete as follows::
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | sodaville.txt | 13 The interrupt specifier consists of two cells encoded as follows:
15 - <2nd cell>: The level-sense information, encoded as follows:
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-generic.rst | 62 The packing of the data follows the MIPI CSI-2 specification and the padding of
106 The packing of the data follows the MIPI CSI-2 specification and the padding of
152 The packing of the data follows the MIPI CSI-2 specification and the padding of
195 The packing of the data follows the MIPI CSI-2 specification and the padding of
244 The packing of the data follows the MIPI CSI-2 specification and the padding of
297 The packing of the data follows the MIPI CSI-2 specification and the padding of
|
| /linux/Documentation/pcmcia/ |
| H A D | locking.rst | 69 The "main" struct pcmcia_socket is protected as follows (read-only fields
112 The "main" struct pcmcia_device is protected as follows (read-only fields
|
| /linux/tools/perf/Documentation/ |
| H A D | jitdump-specification.txt | 48 The flags currently defined are as follows:
53 …ollowed by records. Each record starts with a fixed size header describing the record that follows.
55 The record header is specified in order as follows:
126 The debug_entry describes the source line information. It is defined as follows in order:
164 The EH Frame header follows the Linux Standard Base (LSB) specification as described in the documen…
167 The EH Frame follows the LSB specification as described in the document at https://refspecs.linuxba…
|
| /linux/Documentation/bpf/ |
| H A D | s390.rst | 36 Once on Debian, the build prerequisites can be installed as follows::
62 Latest Clang targeting BPF can be installed as follows::
130 The virtual machine can be started as follows::
153 need to be mounted as follows::
|
| H A D | prog_flow_dissector.rst | 98 The takeaway here is as follows: BPF flow dissector program can be called with
108 ``flow_keys->flags`` might contain optional input flags that work as follows:
129 The reference implementation is organized as follows:
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | blocks.rst | 17 For 32-bit filesystems, limits are as follows:
79 For 64-bit filesystems, limits are as follows:
|
| /linux/tools/memory-model/Documentation/ |
| H A D | control-dependencies.txt | 23 as follows:
50 the original example by eliminating the "if" statement as follows:
60 identical stores on both branches of the "if" statement as follows:
73 Unfortunately, current compilers will transform this as follows at high
146 make sure that MAX is greater than one, perhaps as follows:
171 always true, the compiler can transform this example as follows, again
|
| /linux/Documentation/sound/soc/ |
| H A D | pops-clicks.rst | 23 shutdown and follows some basic rules:-
38 ADC until all the pops have occurred. This follows similar power rules to
|
| /linux/samples/vfio-mdev/ |
| H A D | README.rst | 56 as follows::
75 In the Linux guest VM, dmesg output for the device is as follows:
|
| /linux/Documentation/leds/ |
| H A D | leds-blinkm.rst | 21 The registration follows the scheme::
43 The registration follows the scheme::
|
| /linux/Documentation/virt/kvm/loongarch/ |
| H A D | hypercalls.rst | 40 The parameters are as follows:
66 The template for each hypercall is as follows:
|
| /linux/drivers/staging/media/meson/vdec/ |
| H A D | TODO | 5 stack that follows the latest version of the specification, especially
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | ibm,ndfc.txt | 12 - partition(s) - follows the OF MTD standard for partitions
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-sun | 7 Configuration and Power Interface Specification as follows:
|
| H A D | sysfs-driver-intel-rapid-start | 5 Description: An integer representing a set of wakeup events as follows:
|
| /linux/Documentation/kbuild/ |
| H A D | kconfig-macro-language.rst | 14 can write a makefile like follows::
24 and handles as if the source file were input like follows::
156 to make "info" function print " hello", you can write like follows::
241 Instead, you can do like follows so that any function call is statically
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | ampere_cspmu.rst | 7 Ampere SoC PMU is a generic PMU IP that follows Arm CoreSight PMU architecture.
|
| /linux/Documentation/hwmon/ |
| H A D | mc34vr500.rst | 27 alarms. The interrupts are mapped as follows:
|
| /linux/arch/arm64/boot/dts/renesas/ |
| H A D | r9a08g045s33-smarc-pmod1-type-3a.dtso | 21 * The following switches should be set as follows for SCIF1:
|
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-amd8111.rst | 11 follows.
|
| /linux/Documentation/admin-guide/media/ |
| H A D | qcom_camss.rst | 112 interface, the driver is split into V4L2 sub-devices as follows (8x16 / 8x96):
121 The considerations to split the driver in this particular way are as follows:
137 The media controller pipeline graph is as follows (with connected two / three
|