Searched full:why (Results 1 – 25 of 249) sorted by relevance
12345678910
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 14 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
|
| /Documentation/RCU/ |
| D | rcu.rst | 19 - Why would anyone want to use RCU?
50 thing at a time, why should I wait for a grace period?
68 - Why the name "RCU"?
|
| D | UP.rst | 52 Why is it *not* legal to invoke synchronize_rcu() in this case?
109 Why can't synchronize_rcu() return immediately on UP systems running
115 Why is it *not* legal to invoke synchronize_rcu() in this case?
145 Why can't synchronize_rcu() return immediately on UP systems
|
| D | NMI-RCU.rst | 59 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
107 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
|
| /Documentation/timers/ |
| D | timers-howto.rst | 66 - Why not usleep?
76 - Why not msleep for (1ms - 20ms)?
85 - Why is there no "usleep" / What is a good range?
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 123 merge, say *why* the merge is being done. For a lower-level tree, "why" is
149 Why is that? Back merges will muddy the development history of your own
158 sure to document *why* it was required in the commit message. As always,
190 as always, in such situations, the merge commit should explain why the
222 arisen and be prepared to explain why something abnormal needs to be done.
|
| D | pull-requests.rst | 49 so outline what is contained here, why it should be merged, and what, if
58 to understand what I'm pulling, and why I should pull it. I also
69 what they do and why they do it, but explain the _timing_. What
157 description of that tag (which is why you need to provide good
|
| /Documentation/admin-guide/ |
| D | abi-obsolete.rst | 7 The description of the interface will document the reason why it is
|
| D | tainted-kernels.rst | 8 cause might be the event that got the kernel tainted. That's why bug reports
14 trustworthy. That's also why the kernel will print the tainted state when it
25 why the kernel was tainted is shown after the Process ID ('PID:') and a shortened
52 tainted; any other number indicates the reasons why it is. The easiest way to
152 there should be other information in the log indicating why this tainting
|
| D | reporting-regressions.rst | 148 system's configuration, or application. That's why in the end it's often up to
212 regzbot, the Linux kernel regression tracking bot. That's why you want to bring
291 basis. This is another reason why it's in everybody's interest to regularly test
319 but sometimes bend it to make progress. That's for example why some users had to
323 Why do later versions have to be "compiled with a similar configuration"?
359 What is regression tracking and why should I care about it?
364 true for Linux kernel development as well. That's why Thorsten Leemhuis, the
367 paid for this, that's why the work is done on a best effort basis.
369 Why and how are Linux kernel regressions tracked using a bot?
374 That's why the Linux kernel's regression tracker developed regzbot to facilitate
|
| D | ufs.rst | 15 type of ufs automatically. That's why user must specify type of
|
| D | reporting-issues.rst | 256 development community, and this document. That's why you can't demand
298 face, even if they look small or totally unrelated. That's why you should report
466 your kernel gets enhanced in any way. That's why you should remove or disable
475 module not part of the Linux kernel. That why your might need to uninstall the
487 be such an error if your kernel is tainted. That's why it's in your interest to
489 only reason why this step is here, as this process later will tell you to
497 why the kernel also mentions the taint status when it reports an internal
506 to find out why. Try to eliminate the reason. Often it's caused by one these
567 might be caused by a bit flip due to cosmic radiation. That's why you should
607 That's why you have to find the right place and way to report issues yourself.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 170 See the driver for the exact reasons as to why the packets were
180 why the packets were dropped.
188 FIFO error. See the driver for the exact reasons as to why the
198 reasons as to why the packets were dropped.
|
| /Documentation/trace/rv/ |
| D | monitor_wwnr.rst | 40 - Why do we need this model, so?
|
| /Documentation/power/ |
| D | freezing-of-tasks.rst | 112 IV. Why do we do that?
150 "RJW:> Why we freeze tasks at all or why we freeze kernel threads?
160 So in practice, the 'at all' may become a 'why freeze kernel threads?' and
191 may be undesirable. That's why kernel threads are not freezable by default.
|
| /Documentation/ |
| D | atomic_bitops.txt | 42 which is why the generic version maps to clear_bit_unlock(), see atomic_t.txt.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 9 1-2. Why RDMA controller needed?
25 1-2. Why RDMA controller needed?
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 4 Why the "volatile" type class should not be used
12 kernel code is almost never correct; this document describes why.
|
| /Documentation/sound/designs/ |
| D | jack-controls.rst | 5 Why we need Jack kcontrols
|
| /Documentation/arch/arm/sunxi/ |
| D | clocks.rst | 8 Q: Why is the main 24MHz oscillator gateable? Wouldn't that break the
|
| /Documentation/driver-api/media/drivers/ |
| D | saa7134-devel.rst | 19 - saa7130 - low-price chip, doesn't have mute, that is why all those
|
| /Documentation/PCI/ |
| D | msi-howto.rst | 36 Why use MSIs?
39 There are three reasons why using MSIs can give an advantage over
271 Finding why MSIs are disabled on a device
275 why MSIs may not be enabled for a given device. Your first step should
|
| /Documentation/rust/ |
| D | coding-guidelines.rst | 89 before every ``unsafe`` block, and they explain why the code inside the block is
90 correct/sound, i.e. why it cannot trigger undefined behavior in any case, e.g.:
100 comments show why a call (for functions) or implementation (for traits) actually
168 describing why the code inside is sound.
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 9 # understand why this recursive dependency issue occurs lets consider what
|
| /Documentation/devicetree/bindings/ata/ |
| D | faraday,ftide010.yaml | 19 SATA bridge in order to support SATA. This is why a phandle to that
|
12345678910