Home
last modified time | relevance | path

Searched full:easily (Results 1 – 25 of 606) sorted by relevance

12345678910>>...25

/Linux-v5.10/Documentation/block/
Dcmdline-partition.rst9 It has no MBR, so saves storage space. Bootloader can be easily accessed
11 Users can easily change the partition.
/Linux-v5.10/tools/testing/selftests/net/forwarding/
DREADME5 to easily create and test complex environments.
36 2. Ability to easily provision complex topologies. Testing bridging
/Linux-v5.10/Documentation/hwmon/
Dlm83.rst42 contact us. Note that the LM90 can easily be misdetected as a LM83.
63 The fact that the LM83 is only scarcely used can be easily explained.
/Linux-v5.10/block/partitions/
Dcmdline.c8 * It has no MBR, so saves storage space. Bootloader can be easily accessed
10 * Users can easily change the partition.
/Linux-v5.10/Documentation/admin-guide/
Dabi-testing.rst17 developers can easily notify them if any changes occur.
/Linux-v5.10/include/linux/
Dtypecheck.h7 * Always evaluates to 1 so you may use it easily in comparisons.
/Linux-v5.10/arch/ia64/kernel/
Dsigframe.h10 * Place signal handler args where user-level unwinder can find them easily.
/Linux-v5.10/Documentation/security/
Dlsm-development.rst9 This allows an LSM's code to be easily compared to its goals, and so
/Linux-v5.10/drivers/net/ethernet/mellanox/mlx5/core/
Den_rep.h49 * (neigh_ht). In order to iterate easily over the neigh entries.
127 * addition to the hash table. In order to iterate easily over the
/Linux-v5.10/fs/nfsd/
DMakefile10 # this one should be compiled first, as the tracing macros can easily blow up
/Linux-v5.10/drivers/phy/mediatek/
DKconfig16 so you can easily distinguish them by banks layout.
/Linux-v5.10/arch/csky/include/asm/
Dhighmem.h25 * easily, subsequent pte tables have to be allocated in one physical
/Linux-v5.10/Documentation/security/keys/
Dtrusted-encrypted.rst17 (future) PCR values, so keys are easily migrated to new pcr values, such as
19 blobs under different PCR values, so multiple boots are easily supported.
/Linux-v5.10/arch/nds32/include/asm/
Dhighmem.h13 * easily, subsequent pte tables have to be allocated in one physical
/Linux-v5.10/arch/s390/include/asm/
Djump_label.h23 * can be easily distinguished from a hotpatch generated instruction.
/Linux-v5.10/drivers/gpio/
DTODO115 - Look over and identify any remaining easily converted drivers and
172 - Look over and identify any remaining easily converted drivers and
/Linux-v5.10/Documentation/vm/
Dremap_file_pages.rst32 vm.max_map_count limit more easily due to additional VMAs. See comment for
/Linux-v5.10/arch/mips/include/asm/
Dhighmem.h36 * easily, subsequent pte tables have to be allocated in one physical
/Linux-v5.10/Documentation/networking/
Dsysfs-tagging.rst34 through bind mounting and mounts propagation, a task can easily view
/Linux-v5.10/arch/microblaze/include/asm/
Dhighmem.h33 * easily, subsequent pte tables have to be allocated in one physical
/Linux-v5.10/arch/sparc/include/asm/
Dhighmem.h40 * easily, subsequent pte tables have to be allocated in one physical
/Linux-v5.10/tools/testing/ktest/examples/
Dsnowball.conf9 # directory paths within this directory. This allows you to easily
/Linux-v5.10/arch/x86/include/asm/
Dhighmem.h36 * easily, subsequent pte tables have to be allocated in one physical
/Linux-v5.10/drivers/gpu/drm/amd/amdgpu/
Damdgpu_ras_eeprom.h55 * Represents single table record. Packed to be easily serialized into byte
/Linux-v5.10/arch/powerpc/include/asm/
Dhighmem.h37 * easily, subsequent pte tables have to be allocated in one physical

12345678910>>...25