Searched full:often (Results 1 – 25 of 1035) sorted by relevance
12345678910>>...42
| /Linux-v5.15/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.15/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.15/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.15/Documentation/userspace-api/ |
| D | sysfs-platform_profile.rst | 6 hardware related characteristics are often dynamically configurable. The
7 platform configuration is often automatically adjusted to the current
11 These auto platform adjustment mechanisms often can be configured with
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | simple.txt | 6 (LKMM) is quite complex, with subtle differences in code often having
14 will often have special requirements or idioms. For example, developers
15 of MMIO-based device drivers will often need to use mb(), rmb(), and
75 being completely single-threaded, it is often possible to use library
194 Reading code using these primitives is often also quite helpful.
200 When using locking, there often comes a time when it is necessary
230 controlling how often RCU scans for idle CPUs.
|
| /Linux-v5.15/drivers/media/test-drivers/vidtv/ |
| D | vidtv_mux.h | 37 * @pcr_period_usecs: How often we should send PCR packets.
38 * @si_period_usecs: How often we should send PSI packets.
150 * @pcr_period_usecs: How often we should send PCR packets.
151 * @si_period_usecs: How often we should send PSI packets.
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | reporting-issues.rst | 81 will often be needed anyway to hunt down and fix issues.
291 will often be needed anyway to hunt down and fix issues.*
296 easily happen when it comes to the kernel and often leads to frustration on both
300 kernel.org: these kernels from these vendors are often ancient from the point of
301 Linux development or heavily modified, often both.
310 upstream or forward the report there. In practice that often does not work out
321 example often holds true for the mainline kernels shipped by Debian GNU/Linux
324 its only slightly modified; that for example is often the case for Arch Linux,
332 those often get rejected or ignored, so consider yourself warned. But it's still
345 Reporting an issue that someone else already brought forward is often a waste of
[all …]
|
| /Linux-v5.15/Documentation/networking/devlink/ |
| D | devlink-info.rst | 32 This is usually the serial number of the ASIC, also often available
50 This is usually the serial number of the board, often available in
71 These versions often only update after a reboot, sometimes device reset.
152 Overall firmware version, often representing the collection of
|
| /Linux-v5.15/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.15/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
|
| /Linux-v5.15/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.15/Documentation/userspace-api/media/v4l/ |
| D | colorspaces.rst | 48 The Y value in the CIE XYZ colorspace corresponds to luminance. Often
113 in the CIE XYZ colorspace. Also note that Y'CbCr is often called YCbCr
147 colorspace standards correctly define all four, quite often the
149 standards for the missing pieces. The fact that colorspaces are often a
|
| /Linux-v5.15/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
625 often DMA (especially if the root filesystem is in SPI flash), and
|
| /Linux-v5.15/Documentation/driver-api/gpio/ |
| 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
|
| 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
|
| /Linux-v5.15/Documentation/locking/ |
| D | pi-futex.rst | 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.15/Documentation/doc-guide/ |
| D | contributing.rst | 41 Warnings issued by a compiler for C code can often be dismissed as false
49 Another important point is that documentation warnings are often created by
52 documentation tree is often not the right one to actually carry those
202 current, adding whatever information is needed. Such work often requires
204 course. Developers are often more than willing to cooperate with people
|
| /Linux-v5.15/kernel/kcsan/ |
| D | permissive.h | 62 * that marking them all is often unrealistic and left to maintainer in kcsan_ignore_data_race()
84 * changed) More often than not, they come with interesting in kcsan_ignore_data_race()
|
| /Linux-v5.15/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.15/include/linux/ |
| D | devm-helpers.h | 18 * is typical example where IRQs are often devm-managed and WQs are manually
20 * often the case when we use devm for IRQs) we have a period of time after
|
| /Linux-v5.15/Documentation/driver-api/usb/ |
| D | error-codes.rst | 88 reported. That's because transfers often involve several packets, so that
119 Note that often the controller hardware does
122 protocol error, a failure to respond (often
157 ``-ENODEV`` Device was removed. Often preceded by a burst
|
| /Linux-v5.15/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.15/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.15/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.15/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
|
12345678910>>...42
