/linux/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
|
/linux/Documentation/filesystems/bcachefs/ |
H A D | CodingStyle.rst | 11 Things don't always have to be perfect - nitpicking often does more harm than 61 often nudge you towards making the entire system simpler and more robust. 108 better behaved; often one bug will uncover several other bugs through 130 become product-manager focused. Often time an idea is a good one but needs to 146 Complicated features can often be done as a series of refactorings, with the 160 often go astray - doing something because it seems like it'll be useful often 166 Talk about your ideas with your fellow developers; often times the best things
|
/linux/Documentation/ABI/testing/ |
H A D | sysfs-mce | 9 machine check (often with panic), corrected ones cause a 45 How often to poll for corrected machine check errors, in 48 (poll more often) on the polling interval. When the poller 50 (poll less often) on the polling interval. The check_interval
|
/linux/Documentation/admin-guide/ |
H A D | quickly-build-trimmed-linux.rst | 103 * Install all software required to build a Linux kernel. Often you will need: 171 * In case you want to apply a kernel patch, do so now. Often a command like 208 Using this make target is fine for everybody else, too -- but you often can 223 it is often negligible if such features are missing. But you should keep that 266 Often all left for you to do afterwards is a ``reboot``, as many commodity 473 safe side, so often you will need less. 553 People new to compiling Linux often assume downloading an archive via the 557 be the case, but in practice it often will turn out to be a wrong assumption. 559 That's because when reporting or debugging an issue developers will often ask to 570 A shallow clone therefore is often the better choice. If you nevertheless want [all …]
|
H A D | reporting-issues.rst | 72 will often be needed anyway to hunt down and fix issues. 282 will often be needed anyway to hunt down and fix issues.* 287 easily happen when it comes to the kernel and often leads to frustration on both 291 kernel.org: these kernels from these vendors are often ancient from the point of 292 Linux development or heavily modified, often both. 301 upstream or forward the report there. In practice that often does not work out 312 example often holds true for the mainline kernels shipped by Debian GNU/Linux 315 it's only slightly modified; that for example is often the case for Arch Linux, 323 those often get rejected or ignored, so consider yourself warned. But it's still 336 Reporting an issue that someone else already brought forward is often a waste of [all …]
|
H A D | reporting-regressions.rst | 139 this, but often it's required. 145 own. But for them that's often impossible to do with reasonable effort, as quite 148 system's configuration, or application. That's why in the end it's often up to 257 affected area and often Linus Torvalds himself try very hard to fix security 267 Sadly these things happen, but luckily not very often; if they occur, expert 279 5.15-rc1. All these changes often can simply be reverted and the regression thus 289 It is, but often it's hard to fix such regressions due to the aspects outlined 318 The staging developers nevertheless often adhere to the "no regressions" rule, 320 deal with (often negligible) regressions when a WiFi driver from the staging 332 interfaces often abused by malware, which at the same time are required to run a
|
/linux/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 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/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.
|
/linux/Documentation/process/ |
H A D | 3.Early-stage.rst | 132 subsystem list, posting there is often preferable to posting on 181 posted by others. Beyond that, high-level designs often hide problems 207 considering whether the secrecy is really necessary; there is often no real 215 best option is often to hire an outside developer to review the plans under 222 This kind of review is often enough to avoid serious problems later on
|
H A D | 6.Followthrough.rst | 48 agendas at the expense of your own. Kernel developers often expect to 105 kernel development community; he can often unjam a situation which seems to 123 (memory management patches, for example), the default tree often ends up 141 blessings: before the advent of the linux-next tree, these conflicts often
|
/linux/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
|
/linux/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()
|
/linux/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
|
/linux/Documentation/driver-api/gpio/ |
H A D | intro.rst | 29 often have a few such pins to help with pin scarcity on SOCs; and there are 46 - Inputs can often be used as IRQ signals, often edge triggered but
|
/linux/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 207 current, adding whatever information is needed. Such work often requires 209 course. Developers are often more than willing to cooperate with people
|
/linux/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
|
/linux/Documentation/driver-api/usb/ |
H A 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
|
H A 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 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/kernel/kcsan/ |
H A 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/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
|
/linux/include/linux/ |
H A 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/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 host. 65 Microcontrollers often support both host and target sides of the SPI 87 and if dynamic reconfiguration is important, USB will often be a more 145 processors, and often support both Controller and target roles. 218 Platforms will often abstract the "register SPI controller" operation, 262 * developer boards will often need Linux to do it. 277 on the target board, often with some board-specific data needed for the 609 often DMA (especially if the root filesystem is in SPI flash), and
|
/linux/tools/power/cpupower/man/ |
H A 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/Documentation/sound/soc/ |
H A 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/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
|