| /linux/Documentation/power/regulator/ |
| H A D | design.rst | 5 This document provides a brief, partially structured, overview of some
36 The consumer API should be structured so that these use cases are
|
| /linux/fs/nilfs2/ |
| H A D | Kconfig | 8 NILFS2 is a log-structured file system (LFS) supporting continuous
|
| /linux/Documentation/arch/loongarch/ |
| H A D | booting.rst | 31 a 64-byte header structured like::
|
| /linux/drivers/gpu/drm/ci/ |
| H A D | lava-submit.sh | 87 --structured-log-file "results/lava_job_detail.json" \
|
| /linux/Documentation/driver-api/ |
| H A D | i2c.rst | 18 structured around two kinds of driver, and two kinds of device. An I2C
|
| H A D | spi.rst | 22 The programming interface is structured around two kinds of driver, and
|
| /linux/fs/quota/ |
| H A D | Kconfig | 46 # Generic support for tree structured quota files. Selected when needed.
|
| /linux/Documentation/driver-api/thermal/ |
| H A D | exynos_thermal.rst | 67 The exynos thermal driver is structured as::
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | fsl,imx27-pinctrl.txt | 91 and MUX_ID. They are structured as MX27_PAD_<Pad name>__<Signal name>. The names
|
| /linux/Documentation/admin-guide/ |
| H A D | bootconfig.rst | 16 This allows administrators to pass a structured-Key config file.
21 The boot config syntax is a simple structured key-value. Each key consists
100 structured key, you have to define it outside of the brace. For example::
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | using-gpio.rst | 46 For structured and managed applications, we recommend that you make use of the
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm_ffa_crb.rst | 9 The CRB provides a structured set of control registers a client uses when
|
| /linux/fs/f2fs/ |
| H A D | Kconfig | 19 F2FS is based on Log-structured File System (LFS), which supports
|
| /linux/Documentation/iio/ |
| H A D | adxl380.rst | 227 data is structured.
|
| H A D | adis16550.rst | 370 data is structured.
|
| H A D | adis16475.rst | 378 data is structured.
|
| /linux/Documentation/arch/arm64/ |
| H A D | silicon-errata.rst | 41 available and the code is structured (preferably with a comment) in such
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | paride.rst | 55 To support such a wide range of devices, pata_parport is actually structured
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-self-describing-metadata.rst | 221 A typical buffer read verifier is structured as follows::
246 the case it can't, the code is structured as follows::
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| H A D | internal.rst | 60 The SSAM core implementation is structured in layers, somewhat following the
100 The packet transport layer is represented via |ssh_ptl| and is structured
297 the corresponding callback. The request transport layer is structured around
|
| /linux/Documentation/filesystems/ |
| H A D | f2fs.rst | 14 is based on Log-structured File System (LFS). The design has been focused on
39 Log-structured File System (LFS)
41 "A log-structured file system writes all modifications to disk sequentially in
48 implementation of a log-structured file system", ACM Trans. Computer Systems
|
| H A D | nilfs2.rst | 7 NILFS2 is a log-structured file system (LFS) supporting continuous
|
| /linux/Documentation/core-api/ |
| H A D | packing.rst | 303 structured type with a fixed size. This generally makes it easier for the
|
| /linux/Documentation/usb/ |
| H A D | gadget_printer.rst | 24 This driver is structured for printer firmware that runs in user mode. The
|
| /linux/Documentation/isdn/ |
| H A D | interface_capi.rst | 213 including subparameters of the Additional Info and B Protocol structured
|