Home
last modified time | relevance | path

Searched full:trivial (Results 1 – 25 of 554) sorted by relevance

12345678910>>...23

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/
Dtrivial-rtc.yaml4 $id: http://devicetree.org/schemas/rtc/trivial-rtc.yaml#
7 title: Trivial RTCs
13 This is a list of trivial RTC devices that have simple device tree
/kernel/linux/linux-4.19/Documentation/fmc/
Dfmc-trivial.txt1 fmc-trivial
4 The simple module fmc-trivial is just a simple client that registers an
D00-INDEX31 fmc-trivial.txt
32 - about drivers/fmc/fmc-trivial.ko
Dmezzanine.txt89 see how they are actually used, please look at spec-trivial.c.
113 For example, if you are using the trivial driver to load two different
118 insmod fmc-trivial.ko \
/kernel/linux/linux-4.19/Documentation/translations/zh_CN/
DSubmittingPatches152 (Trivial Patch Monkey)trivial@kernel.org,那里专门收集琐碎的补丁。下面这样
165 EMAIL: trivial@kernel.org
168 违例写一下译注。"trivial"这个英文单词的本意是“琐碎的,不重要的。”但是在这里
173 trivial@kernel.org邮件列表的目的是针对这样的补丁,为提交者提供一个中心,来
/kernel/linux/linux-5.10/include/asm-generic/
Dpgtable-nop4d.h18 * The "pgd_xxx()" functions here are trivial for a folded two-level
48 * allocating and freeing a p4d is trivial: the 1-entry p4d is
Dpgtable-nopmd.h26 * The "pud_xxx()" functions here are trivial for a folded two-level
57 * allocating and freeing a pmd is trivial: the 1-entry pmd is
Dpgtable-nopud.h24 * The "p4d_xxx()" functions here are trivial for a folded two-level
55 * allocating and freeing a pud is trivial: the 1-entry pud is
/kernel/linux/linux-4.19/include/asm-generic/
Dpgtable-nop4d.h18 * The "pgd_xxx()" functions here are trivial for a folded two-level
47 * allocating and freeing a p4d is trivial: the 1-entry p4d is
Dpgtable-nop4d-hack.h23 * The "pgd_xxx()" functions here are trivial for a folded two-level
52 * allocating and freeing a pud is trivial: the 1-entry pud is
Dpgtable-nopmd.h26 * The "pud_xxx()" functions here are trivial for a folded two-level
56 * allocating and freeing a pmd is trivial: the 1-entry pmd is
Dpgtable-nopud.h27 * The "p4d_xxx()" functions here are trivial for a folded two-level
56 * allocating and freeing a pud is trivial: the 1-entry pud is
/kernel/linux/linux-4.19/drivers/fmc/
Dfmc-trivial.c14 /* A trivial fmc driver that can load a gateware file and reports interrupts */
53 ret = fmc_irq_request(fmc, t_handler, "fmc-trivial", IRQF_SHARED); in t_probe()
/kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/configs/rcu/
DTRIVIAL.boot1 rcutorture.torture_type=trivial
/kernel/linux/linux-4.19/fs/hfs/
Dtrans.c24 * the 'trivial' name-mangling scheme, returning the length of the
90 * using the 'trivial' name-mangling scheme, returning the length of
/kernel/linux/linux-5.10/fs/hfs/
Dtrans.c24 * the 'trivial' name-mangling scheme, returning the length of the
90 * using the 'trivial' name-mangling scheme, returning the length of
/kernel/linux/linux-5.10/tools/testing/selftests/x86/
Dtrivial_program.c1 /* Trivial program to check that compilation with certain flags is working. */
Dtrivial_32bit_program.c3 * Trivial program to check that we have a valid 32-bit build environment.
Dtrivial_64bit_program.c3 * Trivial program to check that we have a valid 64-bit build environment.
/kernel/linux/linux-4.19/tools/testing/selftests/x86/
Dtrivial_program.c1 /* Trivial program to check that compilation with certain flags is working. */
Dtrivial_32bit_program.c2 * Trivial program to check that we have a valid 32-bit build environment.
Dtrivial_64bit_program.c2 * Trivial program to check that we have a valid 64-bit build environment.
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/progs/
Dbtf_dump_test_case_syntax.c44 * While previous function pointers are pretty trivial (C-syntax-level
45 * trivial), the following are deciphered here for future generations:
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/auxdisplay/
Dimg-ascii-lcd.txt17 from the compatible string, making this binding somewhat trivial.
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/auxdisplay/
Dimg-ascii-lcd.txt17 from the compatible string, making this binding somewhat trivial.

12345678910>>...23