Searched full:often (Results 1 – 25 of 986) sorted by relevance
12345678910>>...40
| /Linux-v5.4/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 9 features; as is often the case with such tools, there are right and wrong
11 of rebasing and merging. Maintainers often get in trouble when they use
20 merging a little too often.
72 as the new base. The kernel is often in a relatively unstable state
85 patch series that has clearly been reparented, often to a random commit,
144 type of merge is often called a "back merge". Back merges can help to make
154 hide interactions with other trees that should not be happening (often) in
172 resolution - often better than the developers involved.
194 Often, though, dependency issues indicate that a change of approach is
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | machinecheck.rst | 9 (often with panic), corrected ones cause a machine check log entry.
40 How often to poll for corrected machine check errors, in seconds
42 finds MCEs it triggers an exponential speedup (poll more often) on
44 triggers an exponential backoff (poll less often) on the polling
|
| /Linux-v5.4/Documentation/sound/designs/ |
| D | powersave.rst | 35 state. Also, it often takes certain time to wake up from the
36 power-down to the active state. These are often hardly to fix, so
43 Try to turn it off when you experience such a thing too often.
|
| /Linux-v5.4/Documentation/admin-guide/aoe/ |
| D | udev-install.sh | 7 # find udev.conf, often /etc/udev/udev.conf
22 # find the directory where udev rules are stored, often
|
| /Linux-v5.4/Documentation/process/ |
| D | 3.Early-stage.rst | 132 subsystem list, posting there is often preferable to posting on
180 posted by others. Beyond that, high-level designs often hide problems
206 considering whether the secrecy is really necessary; there is often no real
214 best option is often to hire an outside developer to review the plans under
221 This kind of review is often enough to avoid serious problems later on
|
| D | 5.Posting.rst | 163 changelogs is a crucial but often-neglected art; it's worth spending
226 - Acked-by: indicates an agreement by another developer (often a
238 patch; this tag is used to give credit to the (often underappreciated)
257 by the mail client will not apply at the other end, and often will not
307 obvious maintainer, Andrew Morton is often the patch target of last resort.
|
| D | 6.Followthrough.rst | 48 agendas at the expense of your own. Kernel developers often expect to
98 kernel development community; he can often unjam a situation which seems to
116 (memory management patches, for example), the default tree often ends up
134 blessings: before the advent of the linux-next tree, these conflicts often
|
| D | 4.Coding.rst | 92 Abstraction layers which hide access to hardware - often to allow the bulk
147 often does not apply to contemporary hardware. Space *is* time, in that a
200 It is often argued that a regression can be justified if it causes things
238 potential errors. Quite often, these warnings point to real problems.
335 Documentation has often been more the exception than the rule with kernel
375 note that, often, comments are most notable by their absence. Once again,
|
| /Linux-v5.4/fs/efs/ |
| D | file.c | 24 * i have no idea why this happens as often as it does in efs_get_block()
48 * i have no idea why this happens as often as it does in efs_bmap()
|
| /Linux-v5.4/Documentation/spi/ |
| D | spi-summary.rst | 14 The three signal wires hold a clock (SCK, often on the order of 10 MHz),
26 other signals, often including an interrupt to the master.
65 Microcontrollers often support both master and slave sides of the SPI
87 and if dynamic reconfiguration is important, USB will often be a more
145 processors, and often support both Master and Slave roles.
221 Platforms will often abstract the "register SPI controller" operation,
265 * developer boards will often need Linux to do it.
280 on the target board, often with some board-specific data needed for the
339 Developer boards often play by different rules than product boards, and one
622 often DMA (especially if the root filesystem is in SPI flash), and
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | colorspaces.rst | 55 The Y value in the CIE XYZ colorspace corresponds to luminance. Often
120 in the CIE XYZ colorspace. Also note that Y'CbCr is often called YCbCr
154 colorspace standards correctly define all four, quite often the
156 standards for the missing pieces. The fact that colorspaces are often a
|
| /Linux-v5.4/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 17 often preferable to use Linux runtime capabilities rather than file
23 CAP_SET{U/G}ID capabilities, this is often at odds with the goals of running a
27 especially since programs often only call setuid() to drop privileges to a
|
| /Linux-v5.4/Documentation/driver-api/gpio/ |
| D | intro.rst | 41 often have a few such pins to help with pin scarcity on SOCs; and there are
58 - Inputs can often be used as IRQ signals, often edge triggered but
|
| D | legacy.rst | 25 often have a few such pins to help with pin scarcity on SOCs; and there are
42 - Inputs can often be used as IRQ signals, often edge triggered but
62 is not the main issue; GPIOs are often used for the kind of board-specific
133 One of the next things to do with a GPIO, often in board setup code when
265 several hundred potential GPIOs, but often only a dozen are used on any
403 or free_irq(). They will often be stored into IRQ resources for platform
547 Most often a gpio_chip is part of an instance-specific structure with state
589 available, from arch_initcall() or earlier; they can often serve as IRQs.
595 function devices, FPGAs or CPLDs -- most often board-specific code handles
597 numbers to use with gpiochip_add(). Their numbers often start right after
|
| /Linux-v5.4/Documentation/ |
| D | pi-futex.txt | 33 technique that often cannot be replaced with lockless algorithms. As we
38 algorithms often endangers to ability to do robust reviews of said code.
39 I.e. critical RT apps often choose lock structures to protect critical
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
27 whatever bus they sit on (often the platform bus) and SPI, and expose
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | error-codes.rst | 85 reported. That's because transfers often involve several packets, so that
116 Note that often the controller hardware does
119 protocol error, a failure to respond (often
154 ``-ENODEV`` Device was removed. Often preceded by a burst
|
| D | URB.rst | 192 which often means some sort of lock will be needed to prevent the URB
233 These are often called in atomic context.
243 also have to set ``urb->interval`` to say how often to make transfers; it's
244 often one per frame (which is once every microframe for highspeed devices).
|
| /Linux-v5.4/tools/power/cpupower/man/ |
| D | cpupower-idle-info.1 | 33 processor. This often is the case on the X86 architecture when the acpi_idle
36 On recent X86 platforms it is often possible to read out hardware registers
|
| /Linux-v5.4/Documentation/sound/soc/ |
| D | overview.rst | 11 * Codec drivers were often tightly coupled to the underlying SoC
17 event). These are quite common events on portable devices and often require
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | lm78.rst | 69 It is a value in volts. When it is unconnected, you will often find the
79 The LM7* only updates its values each 1.5 seconds; reading it more often
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | platform.rst | 85 As a rule, platform specific (and often board-specific) setup code will
99 that are populated on a given board. Without such tables, often the
106 will often provide additional information using the device's platform_data
129 an operating system will be wrong often enough to make trouble.
|
| /Linux-v5.4/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 77 (often 2-nd UART) will not work if this is enabled.
84 (often 1-nd UART) will not work if this is enabled.
|
| /Linux-v5.4/scripts/ |
| D | Makefile.extrawarn | 21 # W=1 - warnings which may be relevant and do not occur too often
56 # W=2 - warnings which occur quite often but may still be relevant
|
| /Linux-v5.4/include/linux/ |
| D | nfs_iostat.h | 79 * show the rate at which VFS requests are made, and how often the
87 * change the size of a file (such operations can often be the
|
12345678910>>...40
