Home
last modified time | relevance | path

Searched full:few (Results 1 – 25 of 1598) sorted by relevance

12345678910>>...64

/linux/arch/arm/common/
H A Dvlock.S19 #define FEW(x...) macro
22 #define FEW(x...) x macro
72 FEW( ldr r2, [r0, #VLOCK_VOTING_OFFSET] )
/linux/tools/testing/selftests/bpf/prog_tests/
H A Dget_branch_snapshot.c112 /* 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/fs/nilfs2/
H A DKconfig11 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/tools/include/nolibc/
H A Dstd.h10 /* 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
H A Dnolibc.h26 * 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/Documentation/ABI/testing/
H A Dsysfs-bus-bcma14 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/Documentation/devicetree/bindings/mips/
H A Dmscc.txt14 The SoC has a few registers (DEVCPU_GCB:CHIP_REGS) handling miscellaneous
30 The SoC has a few registers (HSIO) handling miscellaneous functionalities:
/linux/Documentation/driver-api/firmware/
H A Dbuilt-in-fw.rst14 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/Documentation/devicetree/bindings/clock/
H A Dmicrochip,pic32.txt3 Microchip clock controller is consists of few oscillators, PLL, multiplexer
4 and few divider modules.
H A Dbrcm,bcm2835-cprman.txt9 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/include/linux/
H A Dzconf.h14 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
H A Ddevm-helpers.h41 * 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/drivers/net/ethernet/natsemi/
H A DKconfig25 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/drivers/gpu/drm/i915/
H A DTODO.txt12 - 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/fs/netfs/
H A DKconfig20 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/Documentation/leds/
H A Dledtrig-usbport.rst18 1) Device with single USB LED and few physical ports
24 2) Device with a physical port handled by few controllers
/linux/samples/livepatch/
H A Dlivepatch-shadow-mod.c29 * 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/Documentation/admin-guide/
H A Dreporting-issues.rst62 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/arch/nios2/lib/
H A Dmemcpy.c167 /* 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/arch/x86/include/uapi/asm/
H A Ddebugreg.h14 /* 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/Documentation/devicetree/bindings/
H A Dsubmitting-patches.rst18 Few subsystems, like ASoC, media, regulators and SPI, expect reverse order
74 maintainers after a few weeks, go ahead and take it.
/linux/Documentation/driver-api/driver-model/
H A Ddesign-patterns.rst5 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/Documentation/devicetree/bindings/mtd/
H A Draw-nand-chip.yaml63 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
/linux/arch/arm/mach-omap2/
H A Dprm2xxx.h29 * With a few exceptions, these are the register names beginning with
88 * With a few exceptions, these are the register names beginning with
/linux/Documentation/arch/x86/
H A Dorc-unwinder.rst76 The ORC data format does have a few downsides compared to DWARF. ORC
112 Objtool still needs a few annotations, but only in code which does
118 gives more accurate debuginfo, with very few annotations. It also

12345678910>>...64