| /OK3568_Linux_fs/kernel/Documentation/maintainer/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/x86/x86_64/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/tools/memory-model/Documentation/ |
| H A 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
195 Reading code using these primitives is often also quite helpful.
201 When using locking, there often comes a time when it is necessary
231 controlling how often RCU scans for idle CPUs.
|
| /OK3568_Linux_fs/kernel/Documentation/sound/designs/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/drivers/media/test-drivers/vidtv/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/networking/devlink/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A 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
|
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/spi/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/gpio/ |
| H A 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
|
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/aoe/ |
| H A D | udev-install.sh | 7 # find udev.conf, often /etc/udev/udev.conf
22 # find the directory where udev rules are stored, often
|
| /OK3568_Linux_fs/kernel/Documentation/doc-guide/ |
| H A 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
|
| /OK3568_Linux_fs/u-boot/drivers/block/ |
| H A D | Kconfig | 9 devices often have a partition table which allows the device to
21 devices often have a partition table which allows the device to
|
| /OK3568_Linux_fs/kernel/fs/efs/ |
| H A 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()
|
| /OK3568_Linux_fs/kernel/Documentation/locking/ |
| H A 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
|
| /OK3568_Linux_fs/external/xserver/doc/ |
| H A D | smartsched | 117 2 The server doesn't call select often enough to detect less
121 3 The server calls select too often when executing fast requests.
174 setting isItTimeToYield too often.
|
| /OK3568_Linux_fs/yocto/poky/documentation/test-manual/ |
| H A D | yocto-project-compatible.rst | 16 because such layers are often created by developers with a particular focus
74 constructed often has unintended consequences. The questions and the script
75 are designed to highlight known issues which are often easy to solve. This
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/usb/ |
| H A 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
|
| /OK3568_Linux_fs/u-boot/include/ |
| H A D | reset.h | 15 * known-good initial state. Drivers will often reset HW modules when they
17 * or in response to some error condition. Reset signals are often controlled
23 * controller will often implement multiple separate reset signals, since the
24 * hardware it manages often has this capability. reset-uclass.h describes the
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/LSM/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/driver-model/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/net/ |
| H A D | Kconfig | 19 in the kernel and the tools often go hand in hand. The tools are
137 firewalls often require changes to the programs running on the local
139 they are often combined with a packet filter, which only works if
155 using a mechanism called portforwarding. Masquerading is also often
|