| /linux/Documentation/admin-guide/blockdev/drbd/ |
| H A D | figures.rst | 8 .. kernel-figure:: DRBD-8.3-data-packets.svg
12 .. kernel-figure:: DRBD-data-packets.svg
20 .. kernel-figure:: conn-states-8.dot
24 .. kernel-figure:: disk-states-8.dot
28 .. kernel-figure:: peer-states-8.dot
|
| /linux/Documentation/translations/zh_CN/doc-guide/ |
| H A D | sphinx.rst | 328 如果要添加图片，应该使用 ``kernel-figure`` 和 ``kernel-image`` 指令。例如，
331 .. kernel-figure:: ../../../doc-guide/svg_image.svg
338 .. kernel-figure:: ../../../doc-guide/svg_image.svg
350 .. kernel-figure:: ../../../doc-guide/hello.dot
357 .. kernel-figure:: ../../../doc-guide/hello.dot
385 *render* 指令包含 *figure* 指令中已知的所有选项，以及选项 ``caption`` 。如果
386 ``caption`` 有值，则插入一个 *figure* 节点，若无，则插入一个 *image* 节点。
|
| /linux/Documentation/translations/it_IT/doc-guide/ |
| H A D | sphinx.rst | 409 Figure ed immagini
412 Se volete aggiungere un'immagine, utilizzate le direttive ``kernel-figure``
416 .. kernel-figure:: ../../../doc-guide/svg_image.svg
423 .. kernel-figure:: ../../../doc-guide/svg_image.svg
428 Le direttive del kernel per figure ed immagini supportano il formato **DOT**,
436 .. kernel-figure:: ../../../doc-guide/hello.dot
443 .. kernel-figure:: ../../../doc-guide/hello.dot
473 La direttiva *render* ha tutte le opzioni della direttiva *figure*, con
475 un nodo *figure* viene aggiunto. Altrimenti verrà aggiunto un nodo *image*.
|
| /linux/Documentation/timers/ |
| H A D | highres.rst | 14 changes in the time(r) related Linux subsystems. Figure #1 (p. 2) shows the
35 also figure #2 (OLS slides p. 15)
49 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
66 Figure #3 (OLS slides p.18) illustrates the transformation.
139 Figure #4 (OLS slides p.20) illustrates the transformation.
205 Figure #5 (OLS slides p.22) illustrates the transformation.
|
| /linux/Documentation/doc-guide/ |
| H A D | sphinx.rst | 475 If you want to add an image, you should use the ``kernel-figure`` and
476 ``kernel-image`` directives. E.g. to insert a figure with a scalable
479 .. kernel-figure:: svg_image.svg
486 .. kernel-figure:: svg_image.svg
491 The kernel figure (and image) directive supports **DOT** formatted files, see
498 .. kernel-figure:: hello.dot
505 .. kernel-figure:: hello.dot
535 The *render* directive has all the options known from the *figure* directive,
536 plus option ``caption``. If ``caption`` has a value, a *figure* node is
|
| /linux/drivers/hwmon/ |
| H A D | ads7871.c | 16 /*From figure 18 in the datasheet*/
30 * From figure 17 in the datasheet
39 /*From figure 18 in the datasheet*/
46 /*From figure 18 in the datasheet*/
|
| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 45 .. kernel-figure:: ExpRCUFlow.svg
119 .. kernel-figure:: ExpSchedFlow.svg
305 .. kernel-figure:: Funnel0.svg
314 .. kernel-figure:: Funnel1.svg
320 .. kernel-figure:: Funnel2.svg
349 .. kernel-figure:: Funnel3.svg
356 .. kernel-figure:: Funnel4.svg
363 .. kernel-figure:: Funnel5.svg
370 .. kernel-figure:: Funnel6.svg
377 .. kernel-figure:: Funnel7.svg
[all …]
|
| /linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 245 .. kernel-figure:: rcu_node-lock.svg
276 figure:
278 .. kernel-figure:: TreeRCU-callback-registry.svg
344 .. kernel-figure:: TreeRCU-gp-init-1.svg
366 .. kernel-figure:: TreeRCU-gp-init-2.svg
373 .. kernel-figure:: TreeRCU-gp-init-3.svg
413 .. kernel-figure:: TreeRCU-qs.svg
488 .. kernel-figure:: TreeRCU-dyntick.svg
511 .. kernel-figure:: TreeRCU-hotplug.svg
532 .. kernel-figure:: TreeRCU-gp-fqs.svg
[all …]
|
| /linux/sound/soc/codecs/ |
| H A D | ak4458.h | 51 * x 1 0 MSB justified Figure 3 (default)
52 * x 1 1 I2S Compliment Figure 4
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A D | mpo-overview.rst | 89 .. kernel-figure:: mpo-cursor.svg
126 .. kernel-figure:: single-display-mpo.svg
188 .. kernel-figure:: multi-display-hdcp-mpo.svg
223 .. kernel-figure:: multi-display-hdcp-mpo-less-pipe-ex.svg
|
| /linux/arch/s390/include/asm/ |
| H A D | user.h | 49 this will be used by gdb to figure out where the data and stack segments
55 /* The rest of this junk is to help gdb figure out what goes where */
|
| /linux/Documentation/driver-api/acpi/ |
| H A D | linuxized-acpica.rst | 33 The following figure depicts the Linux ACPI subsystem where the ACPICA
78 Figure 1. Linux ACPI Software Components
130 illustrated in the following figure::
169 Figure 2. ACPICA -> Linux Upstream Process
205 reduced, but there still are several ones and it takes time to figure
|
| /linux/Documentation/netlabel/ |
| H A D | draft-ietf-cipso-ipsecurity-01.txt | 99 Figure 1. CIPSO Format
177 Figure 2: Standard Tag Format
218 Figure 3. Tag Type 1 Format
253 by the least significant bit of the second byte. Figure 4 graphically
276 Figure 4. Ordering of Bits in Tag 1 Bit Map
304 Figure 5. Tag Type 2 Format
367 Figure 6. Tag Type 5 Format
|
| /linux/include/linux/ |
| H A D | reciprocal_div.h | 29 * version of the algorithm described in Figure 4.1 of the paper.
46 * described in Figure 4.2 of the paper except when "divisor > (1U << 31)" whose
|
| /linux/arch/m68k/include/asm/ |
| H A D | user.h | 55 this will be used by gdb to figure out where the data and stack segments
65 /* The rest of this junk is to help gdb figure out what goes where */
|
| /linux/Documentation/i2c/ |
| H A D | summary.rst | 36 .. kernel-figure:: i2c_bus.svg
61 For the example configuration in the figure above, you will need one driver for
|
| /linux/include/linux/pinctrl/ |
| H A D | pinmux.h | 31 * called by the core to figure out which mux setting it shall map a
49 * driver does not need to figure out whether enabling this function
|
| /linux/arch/arm/include/asm/ |
| H A D | user.h | 51 this will be used by gdb to figure out where the data and stack segments
60 /* The rest of this junk is to help gdb figure out what goes where */
|
| /linux/tools/usb/usbip/ |
| H A D | INSTALL | 34 to figure out how `configure' could check whether to do them, and mail
144 There may be some features `configure' cannot figure out automatically,
147 architectures, `configure' can figure that out, but if it prints a
|
| /linux/drivers/pci/hotplug/ |
| H A D | cpqphp_nvram.c | 288 /* Figure out memory Available */ in store_HRT()
313 /* Figure out prefetchable memory Available */ in store_HRT()
338 /* Figure out IO Available */ in store_HRT()
363 /* Figure out bus Available */ in store_HRT()
|
| /linux/drivers/net/ethernet/hisilicon/hns3/ |
| H A D | hnae3.c | 253 * initialize the figure out client instance in hnae3_register_ae_algo()
291 * un-initialize the figure out client instance in hnae3_unregister_ae_algo()
350 * initialize the figure out client instance in hnae3_register_ae_dev()
|
| /linux/arch/x86/include/asm/ |
| H A D | user_32.h | 99 this will be used by gdb to figure out where the data and stack segments
109 /* The rest of this junk is to help gdb figure out what goes where */
|
| H A D | user_64.h | 100 this will be used by gdb to figure out where the data and stack segments
112 /* The rest of this junk is to help gdb figure out what goes where */
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 25 .. kernel-figure:: BigTreeClassicRCU.svg
92 .. kernel-figure:: HugeTreeClassicRCU.svg
126 following figure:
128 .. kernel-figure:: BigTreePreemptRCUBHdyntickCB.svg
130 This figure shows how ``TREE_RCU``'s and ``PREEMPT_RCU``'s major data
134 Note that each of the data structures in the above figure has its own
233 in the following figure:
235 .. kernel-figure:: TreeMapping.svg
247 .. kernel-figure:: TreeMappingLevel.svg
257 .. kernel-figure:: TreeLevel.svg
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | pci_iov_resource_on_powernv.rst | 235 total_VFs is less than 256, we have the situation in Figure 1.0, where
253 Figure 1.0 Direct map VF(n) BAR space
256 space doesn't need that much, as shown in Figure 1.1::
272 Figure 1.1 Map VF(n) BAR space + extra
|