/linux-6.14.4/arch/arm/common/ |
D | vlock.S | 19 #define FEW(x...) macro 22 #define FEW(x...) x macro 72 FEW( ldr r2, [r0, #VLOCK_VOTING_OFFSET] )
|
/linux-6.14.4/tools/testing/selftests/bpf/prog_tests/ |
D | get_branch_snapshot.c | 112 /* too few entries for the hit/waste test */ in serial_test_get_branch_snapshot() 119 /* Given we stop LBR in software, we will waste a few entries. in serial_test_get_branch_snapshot() 120 * But we should try to waste as few as possible entries. We are at in serial_test_get_branch_snapshot()
|
/linux-6.14.4/fs/nilfs2/ |
D | Kconfig | 11 destroyed just a few seconds ago. Since this file system can keep 15 NILFS2 creates a number of checkpoints every few seconds or per
|
/linux-6.14.4/tools/include/nolibc/ |
D | std.h | 10 /* Declare a few quite common macros and types that usually are in stdlib.h, 11 * stdint.h, ctype.h, unistd.h and a few other common locations. Please place
|
D | nolibc.h | 26 * A few of them are architecture-specific because the syscalls are not all 59 * for a few functions usually found in string.h, ctype.h, or stdlib.h. 71 * only a few common includes, may also be built by simply making the include
|
/linux-6.14.4/Documentation/ABI/testing/ |
D | sysfs-bus-bcma | 14 There are a few types of BCMA cores, they can be identified by 30 Each BCMA core is identified by few fields, including class it
|
/linux-6.14.4/Documentation/devicetree/bindings/mips/ |
D | mscc.txt | 14 The SoC has a few registers (DEVCPU_GCB:CHIP_REGS) handling miscellaneous 30 The SoC has a few registers (HSIO) handling miscellaneous functionalities:
|
/linux-6.14.4/Documentation/driver-api/firmware/ |
D | built-in-fw.rst | 14 There are a few reasons why you might want to consider building your firmware 21 Even if you have these needs there are a few reasons why you may not be
|
/linux-6.14.4/Documentation/devicetree/bindings/clock/ |
D | microchip,pic32.txt | 3 Microchip clock controller is consists of few oscillators, PLL, multiplexer 4 and few divider modules.
|
D | brcm,bcm2835-cprman.txt | 9 few PLLs, and a level of mostly-generic clock generators sourcing from 11 clock generators, but a few (like the ARM or HDMI) will source from
|
/linux-6.14.4/Documentation/devicetree/bindings/pinctrl/ |
D | thead,th1520-pinctrl.yaml | 22 pads only a few of those 6 configurations are valid though, and a few pads in 25 Pinconf is fairly regular except for a few pads in group 1 that either can't
|
/linux-6.14.4/drivers/gpu/drm/i915/ |
D | TODO.txt | 12 - There's a lot of complexity added past few years to make relocations faster. 16 2. Any complexity added in this area past few years which can't be justified
|
/linux-6.14.4/drivers/net/ethernet/natsemi/ |
D | Kconfig | 25 a few Nubus and all known Comm Slot Ethernet cards. If you have 36 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
|
/linux-6.14.4/fs/netfs/ |
D | Kconfig | 20 execution as there are a quite a few stats gathered, and on a 55 execution as there are a quite a few stats gathered, and on a
|
/linux-6.14.4/include/linux/ |
D | zconf.h | 14 plus a few kilobytes for small objects. For example, if you want to reduce 20 that is, 32K for windowBits=15 (default value) plus a few kilobytes
|
D | devm-helpers.h | 41 * detached. A few drivers need delayed work which must be cancelled before 66 * A few drivers need to queue work which must be cancelled before driver
|
/linux-6.14.4/Documentation/leds/ |
D | ledtrig-usbport.rst | 18 1) Device with single USB LED and few physical ports 24 2) Device with a physical port handled by few controllers
|
/linux-6.14.4/samples/livepatch/ |
D | livepatch-shadow-mod.c | 29 * Watch dmesg output for a few moments to see new dummy being allocated 78 /* Check for expired dummies after a few new ones have been allocated */ 80 /* Dummies expire after a few cleanup instances */
|
/linux-6.14.4/Documentation/admin-guide/ |
D | reporting-issues.rst | 62 Note: this section covers a few more aspects than the TL;DR and does things in 121 suspend your efforts for a few days anyway. Whatever version you choose, 145 issue. Always mention a few things: the latest kernel version you installed 211 * Prepare yourself for the possibility that going through the next few steps 245 A few words of general advice before digging into the details: 350 to use good search terms; vary them a few times, too. While doing so try to 503 followed by a few spaces and some letters. 600 it. Quite a few programmers for example only care for just one driver, for 680 Linux kernel development is completely driven by mail. Very few subsystems use 753 quite a few other lists miss a way to search the archives. In those cases use a [all …]
|
/linux-6.14.4/arch/nios2/lib/ |
D | memcpy.c | 167 /* If there not too few bytes to copy, use word copy. */ in memcpy() 169 /* Copy just a few bytes to make DSTP aligned. */ in memcpy() 188 /* There are just a few bytes to copy. Use byte memory operations. */ in memcpy()
|
/linux-6.14.4/arch/x86/include/uapi/asm/ |
D | debugreg.h | 14 /* Define a few things for the status register. We can use this to determine 65 /* The second byte to the control register has a few special things.
|
/linux-6.14.4/Documentation/driver-api/driver-model/ |
D | design-patterns.rst | 5 This document describes a few common design patterns found in device drivers. 16 While the kernel contains a few device drivers that assume that they will
|
/linux-6.14.4/Documentation/devicetree/bindings/ |
D | submitting-patches.rst | 18 Few subsystems, like ASoC, media, regulators and SPI, expect reverse order 74 maintainers after a few weeks, go ahead and take it.
|
/linux-6.14.4/arch/arm/mach-omap2/ |
D | prm2xxx.h | 29 * With a few exceptions, these are the register names beginning with 88 * With a few exceptions, these are the register names beginning with
|
/linux-6.14.4/Documentation/devicetree/bindings/mtd/ |
D | raw-nand-chip.yaml | 63 a few blocks at the end of the device to store it and update 65 few pages of all the blocks will be scanned at boot time to
|