| /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/drivers/net/wireless/intel/iwlwifi/fw/ |
| H A D | error-dump.h | 20 * @IWL_FW_ERROR_DUMP_TXCMD: last TX command data, structured as 31 * Structured as &struct iwl_fw_error_dump_trigger_desc. 32 * @IWL_FW_ERROR_DUMP_RB: the content of an RB structured as 42 * which we get from the fw after ALIVE. The content is structured as
|
| /linux/fs/nilfs2/ |
| H A D | Kconfig | 8 NILFS2 is a log-structured file system (LFS) supporting continuous
|
| /linux/tools/lib/python/kdoc/ |
| H A D | kdoc_item.py | 35 # structured data, this will, hopefully, fade away.
|
| /linux/Documentation/mm/ |
| H A D | index.rst | 47 algorithms. It should all be integrated nicely into the above structured
|
| /linux/fs/quota/ |
| H A D | Kconfig | 36 # Generic support for tree structured quota files. Selected when needed.
|
| /linux/arch/riscv/kernel/ |
| H A D | compat_signal.c | 108 /* sc_regs is structured the same as the start of pt_regs */ in compat_restore_sigcontext() 170 /* sc_regs is structured the same as the start of pt_regs */ in compat_setup_sigcontext()
|
| /linux/Documentation/arch/loongarch/ |
| H A D | booting.rst | 31 a 64-byte header structured like::
|
| /linux/rust/syn/ |
| H A D | attr.rs | 123 /// # Parsing from Attribute to structured arguments 345 /// In some cases, for attributes which have nested layers of structured 454 /// Content of a compile-time structured attribute. 478 /// A structured list within an attribute, like `derive(Copy, Clone)`. 487 /// A structured list within an attribute, like `derive(Copy, Clone)`. 507 /// Returns the path that begins this structured meta item.
|
| H A D | meta.rs | 3 //! Facility for interpreting structured content inside of an `Attribute`. 145 /// structured attributes. 210 /// nested parentheses is also expected to conform to Rust's structured
|
| /linux/Documentation/arch/arm/spear/ |
| H A D | overview.rst | 8 SPEAr (Structured Processor Enhanced Architecture).
|
| /linux/arch/s390/include/uapi/asm/ |
| H A D | raw3270.h | 11 #define TC_WRITESF 0x11 /* Write structured field */
|
| /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 | generic_pt.rst | 16 Generic PT is structured as a multi-compilation system. Since each format
|
| /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/driver-api/thermal/ |
| H A D | exynos_thermal.rst | 67 The exynos thermal driver is structured as::
|
| /linux/Documentation/driver-api/usb/ |
| H A D | typec.rst | 103 Structured VDM "Discover Identity", the port driver needs to register the cable 158 Delivery Structured VDM Discover SVIDs message, each SVID needs to be
|
| /linux/fs/f2fs/ |
| H A D | Kconfig | 19 F2FS is based on Log-structured File System (LFS), which supports
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | mediatek,mt8196-sys-clock.yaml | 14 The clock architecture in MediaTek SoCs is structured like below:
|
| H A D | mediatek,mt8196-clock.yaml | 14 The clock architecture in MediaTek SoCs is structured like below:
|
| /linux/include/uapi/linux/ |
| H A D | nbd.h | 79 /* magic 0x668e33ef for structured reply not supported by kernel yet */
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-dmi-entries | 15 DMI is structured as a large table of entries, where
|
| /linux/drivers/gpu/drm/imagination/ |
| H A D | pvr_drv.h | 40 * Macros used to aid copying structured and array data to and from
|
| /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
|