Home
last modified time | relevance | path

Searched full:laid (Results 1 – 25 of 217) sorted by relevance

123456789

/kernel/linux/linux-6.6/drivers/md/
Draid10.h37 int near_copies; /* number of copies laid out
39 int far_copies; /* number of copies laid out
/kernel/linux/linux-5.10/drivers/md/
Draid10.h37 int near_copies; /* number of copies laid out
39 int far_copies; /* number of copies laid out
/kernel/linux/linux-6.6/include/drm/
Ddrm_fourcc.h148 * format with data laid in a single plane
162 * format with data laid in two planes (luminance and chrominance)
176 * format with data laid in three planes (one for each YUV component)
/kernel/linux/linux-5.10/include/drm/
Ddrm_fourcc.h148 * format with data laid in a single plane
162 * format with data laid in two planes (luminance and chrominance)
176 * format with data laid in three planes (one for each YUV component)
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-driver-tegra-fuse6 data programmed at the factory. The data is laid out in 32bit
/kernel/linux/linux-5.10/drivers/net/ethernet/intel/igc/
Digc_diag.h16 /* In the hardware, registers are laid out either singly, in arrays
/kernel/linux/linux-6.6/drivers/net/ethernet/intel/igc/
Digc_diag.h16 /* In the hardware, registers are laid out either singly, in arrays
/kernel/linux/linux-6.6/Documentation/scsi/
Dsym53c500_cs.rst22 other products using this chip, but I've never laid eyes (much less hands)
/kernel/linux/linux-5.10/Documentation/scsi/
Dsym53c500_cs.rst22 other products using this chip, but I've never laid eyes (much less hands)
/kernel/linux/linux-5.10/tools/testing/selftests/arm64/signal/
Dsignals.S48 * For simplicity this assumes that current field 'token' is laid out
/kernel/linux/linux-6.6/include/linux/
Dpacking.h22 * format. Unpacked means laid out in memory in the CPU's native
Dlitex.h30 * 32-bit wide logical CSR will be laid out as four 32-bit physical
Dpage-flags-layout.h40 * There are five possibilities for how page->flags get laid out. The first
/kernel/linux/linux-6.6/tools/testing/selftests/arm64/signal/
Dsignals.S48 * For simplicity this assumes that current field 'token' is laid out
/kernel/linux/linux-5.10/include/linux/
Dpacking.h22 * format. Unpacked means laid out in memory in the CPU's native
Dpage-flags-layout.h39 * There are five possibilities for how page->flags get laid out. The first
/kernel/linux/linux-6.6/include/uapi/rdma/
Dcxgb4-abi.h41 * Make sure that all structs defined in this file remain laid out so
Dmthca-abi.h47 * Make sure that all structs defined in this file remain laid out so
/kernel/linux/linux-5.10/include/uapi/rdma/
Dcxgb4-abi.h41 * Make sure that all structs defined in this file remain laid out so
Dmthca-abi.h47 * Make sure that all structs defined in this file remain laid out so
/kernel/linux/linux-5.10/arch/sparc/include/uapi/asm/
Dpsr.h15 /* The Sparc PSR fields are laid out as the following:
/kernel/linux/linux-6.6/arch/sparc/include/uapi/asm/
Dpsr.h15 /* The Sparc PSR fields are laid out as the following:
/kernel/linux/linux-6.6/arch/openrisc/include/asm/
Dptrace.h31 * This struct describes how the registers are laid out on the kernel stack
/kernel/linux/linux-5.10/arch/openrisc/include/asm/
Dptrace.h31 * This struct describes how the registers are laid out on the kernel stack
/kernel/linux/linux-5.10/Documentation/block/
Ddeadline-iosched.rst63 or a front merge candidate. Due to the way files are typically laid out,

123456789