| /kernel/linux/linux-5.10/drivers/media/pci/bt8xx/ |
| D | bttv-audio-hook.c | 60 /* Not much to do here */ in gvbctv3pci_audio()
162 /* Not much to do here */ in avermedia_tvphone_audio()
193 /* Not much to do here */ in avermedia_tv_stereo_audio()
231 /* Not much to do here */ in lt9415_audio()
264 /* Not much to do here */ in terratv_audio()
297 /* Not much to do here */ in winfast2000_audio()
344 /* Not much to do here */ in pvbt878p9b_audio()
385 /* Not much to do here */ in fv2000s_audio()
421 /* Not much to do here */ in windvr_audio()
458 /* Not much to do here */ in adtvk503_audio()
|
| /kernel/linux/linux-6.6/drivers/media/pci/bt8xx/ |
| D | bttv-audio-hook.c | 60 /* Not much to do here */ in gvbctv3pci_audio()
162 /* Not much to do here */ in avermedia_tvphone_audio()
193 /* Not much to do here */ in avermedia_tv_stereo_audio()
231 /* Not much to do here */ in lt9415_audio()
264 /* Not much to do here */ in terratv_audio()
336 /* Not much to do here */ in pvbt878p9b_audio()
377 /* Not much to do here */ in fv2000s_audio()
413 /* Not much to do here */ in windvr_audio()
450 /* Not much to do here */ in adtvk503_audio()
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | orc-unwinder.rst | 12 format of the ORC data is much simpler than DWARF, which in turn allows
13 the ORC unwinder to be much simpler and faster.
63 ORC debuginfo's advantage over DWARF itself is that it's much simpler.
66 much simpler, meaning fewer bugs, which is especially important for
69 The simpler debuginfo format also enables the unwinder to be much faster
114 annotations are needed than what DWARF would need, so they're much more
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | orc-unwinder.rst | 12 format of the ORC data is much simpler than DWARF, which in turn allows
13 the ORC unwinder to be much simpler and faster.
63 ORC debuginfo's advantage over DWARF itself is that it's much simpler.
66 much simpler, meaning fewer bugs, which is especially important for
69 The simpler debuginfo format also enables the unwinder to be much faster
114 annotations are needed than what DWARF would need, so they're much more
|
| /kernel/linux/linux-6.6/arch/arm64/kernel/ |
| D | watchdog_hld.c | 10 * Arm CPUs in the market which are clocked much less than 5 GHz. On the other
11 * hand, we can't make it much higher as it would lead to a large hard-lockup
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | timex.h | 90 * SHIFT_PLL is used as a dampening factor to define how much we
93 * much of the current value in time_offset we correct for each
100 * However this seems to increase convergence time much too long.
114 * SHIFT_FLL is used as a dampening factor to define how much we
|
| D | zstd.h | 296 * @output: Destination buffer. `output->pos` is updated to indicate how much
298 * @input: Source buffer. `input->pos` is updated to indicate how much data
316 * @output: Destination buffer. `output->pos` is updated to indicate how much
331 * @output: Destination buffer. `output->pos` is updated to indicate how much
383 * @output: Destination buffer. `output.pos` is updated to indicate how much
385 * @input: Source buffer. `input.pos` is updated to indicate how much data was
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | timex.h | 90 * SHIFT_PLL is used as a dampening factor to define how much we
93 * much of the current value in time_offset we correct for each
100 * However this seems to increase convergence time much too long.
114 * SHIFT_FLL is used as a dampening factor to define how much we
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 14 actually only used once interfaces. But the clear downside is that there's much
110 paths pretty much for free for graphics drivers. Also, be consistent with
160 an asynchronous event on a pollable file descriptor. It fits much better
208 it's much quicker to push a driver-private interface than engaging in
214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | botching-up-ioctls.rst | 14 actually only used once interfaces. But the clear downside is that there's much
110 paths pretty much for free for graphics drivers. Also, be consistent with
160 an asynchronous event on a pollable file descriptor. It fits much better
208 it's much quicker to push a driver-private interface than engaging in
214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | floppy.h | 42 * driver otherwise. It doesn't matter much for performance anyway, as most
47 * Actually this needs to be a bit more complicated since the so much different
|
| /kernel/linux/linux-6.6/arch/mips/include/asm/ |
| D | floppy.h | 42 * driver otherwise. It doesn't matter much for performance anyway, as most
47 * Actually this needs to be a bit more complicated since the so much different
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | sched-nice-design.rst | 9 pestered us to make nice +19 tasks use up much less CPU time.
17 much stronger than they were before in 2.4 (and people were happy about
39 So that if someone wanted to really renice tasks, +19 would give a much
|
| D | sched-design-CFS.rst | 65 side of the tree as much as possible.
108 The CFS scheduler has a much stronger handling of nice levels and SCHED_BATCH
109 than the previous vanilla scheduler: both types of workloads are isolated much
150 without the core code assuming too much about them.
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-nice-design.rst | 9 pestered us to make nice +19 tasks use up much less CPU time.
17 much stronger than they were before in 2.4 (and people were happy about
39 So that if someone wanted to really renice tasks, +19 would give a much
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | index.rst | 15 documentation, like the kernel itself, is very much a work in progress;
72 merged much easier.
91 from the point of view of a kernel developer. Much of the information here
|
| /kernel/linux/linux-6.6/rust/alloc/collections/ |
| D | mod.rs | 73 reason = "Uncertain how much info should be exposed",
85 reason = "Uncertain how much info should be exposed",
113 reason = "Uncertain how much info should be exposed",
|
| /kernel/linux/linux-6.6/Documentation/ |
| D | subsystem-apis.rst | 8 from the point of view of a kernel developer. Much of the information here
63 **Fixme**: much more organizational work is needed here.
|
| /kernel/linux/linux-6.6/Documentation/powerpc/ |
| D | kasan.txt | 48 this at run-time based on how much physical memory we have, but this requires
54 requires knowing how much contiguous physical memory a system has _at compile
|
| /kernel/linux/linux-6.6/net/batman-adv/ |
| D | bitarray.c | 60 /* sequence number is much newer, probably missed a lot of packets */ in batadv_bit_get_packet()
72 /* received a much older packet. The other host either restarted in batadv_bit_get_packet()
|
| /kernel/linux/linux-5.10/net/batman-adv/ |
| D | bitarray.c | 60 /* sequence number is much newer, probably missed a lot of packets */ in batadv_bit_get_packet()
72 /* received a much older packet. The other host either restarted in batadv_bit_get_packet()
|
| /kernel/linux/linux-6.6/lib/zstd/common/ |
| D | error_private.c | 29 … case PREFIX(frameParameter_windowTooLarge): return "Frame requires too much memory for decoding"; in ERR_getErrorString()
38 case PREFIX(tableLog_tooLarge): return "tableLog requires too much memory : unsupported"; in ERR_getErrorString()
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | resource.h | 76 * The first two don't need much. The latter will take as
77 * much as it can get. 8MB is a reasonably sane default.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/driver-model/ |
| D | devres.rst | 15 5. Overhead : How much do we have to pay for this?
35 For one reason or another, low level drivers don't receive as much
38 Init failure path is worse because it's much less travelled while
102 driver can have much simpler init and exit code. Init path basically
|
| /kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
| D | devres.rst | 15 5. Overhead : How much do we have to pay for this?
35 For one reason or another, low level drivers don't receive as much
38 Init failure path is worse because it's much less travelled while
102 driver can have much simpler init and exit code. Init path basically
|