Searched full:things (Results 1 – 25 of 4466) sorted by relevance
12345678910>>...179
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | opp.rst | 117 /* Do things */
123 /* Do cpufreq things */
125 /* Do remaining things */
263 /* do things */
269 /* do other things */
280 /* do things.. */
288 /* do other things */
296 /* do things.. */
306 /* Do things */
319 /* Do other things */
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | opp.rst | 117 /* Do things */
123 /* Do cpufreq things */
125 /* Do remaining things */
263 /* do things */
269 /* do other things */
280 /* do things.. */
288 /* do other things */
296 /* do things.. */
306 /* Do things */
319 /* Do other things */
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | 6.Followthrough.rst | 28 process. Life can be made much easier, though, if you keep a few things in
56 the kernel. One job the maintainers do is to keep things looking
65 understand what the reviewer is trying to say. If possible, fix the things
75 agree with the reviewer, take some time to think things over again. It can
99 What if you've tried to do everything right and things still aren't going
118 things. In particular, there may be more than one tree - one, perhaps,
192 Other things that can happen
|
| D | howto.rst | 56 of doing things.
130 not have a stable API within the kernel, including things like:
385 you want to bring up, before you post it to the list. A lot of things
448 again, sometimes things get lost in the huge volume.
465 of a dozen things you should correct. This does **not** imply that your
475 development environments. Here are a list of things that you can try to
478 Good things to say regarding your proposed changes:
487 Bad things you should avoid saying:
532 The reasons for breaking things up are the following:
602 All of these things are sometimes very hard to do. It can take years to
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | frame-buffer.rst | 15 that are user defined. With fb_var_screeninfo, things such as depth
25 importance for fb_monospecs. This allowed for forbidden things such as
27 fb_monospecs prevents such things, and if used correctly, can prevent a
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | frame-buffer.rst | 15 that are user defined. With fb_var_screeninfo, things such as depth
25 importance for fb_monospecs. This allowed for forbidden things such as
27 fb_monospecs prevents such things, and if used correctly, can prevent a
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 6.Followthrough.rst | 28 process. Life can be made much easier, though, if you keep a few things in
58 understand what the reviewer is trying to say. If possible, fix the things
68 agree with the reviewer, take some time to think things over again. It can
92 What if you've tried to do everything right and things still aren't going
111 things. In particular, there may be more than one tree - one, perhaps,
185 Other things that can happen
|
| D | howto.rst | 56 of doing things.
130 not have a stable API within the kernel, including things like:
386 you want to bring up, before you post it to the list. A lot of things
449 again, sometimes things get lost in the huge volume.
466 of a dozen things you should correct. This does **not** imply that your
476 development environments. Here are a list of things that you can try to
479 Good things to say regarding your proposed changes:
488 Bad things you should avoid saying:
533 The reasons for breaking things up are the following:
603 All of these things are sometimes very hard to do. It can take years to
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/include/uapi/asm/ |
| D | debugreg.h | 14 /* Define a few things for the status register. We can use this to determine
30 /* Now define a bunch of things for manipulating the control register.
64 /* The second byte to the control register has a few special things.
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | bus-virt-phys-mapping.rst | 42 things any more complex than necessary, so you can assume that all
46 address, and things are very simple indeed. However, they are that simple
145 buffer), but can be things like a packet buffer in a network card etc.
156 For such memory, you can do things like:
211 don't do all that complex things (or rather: the complexity is not so
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | ftrace-design.rst | 15 code relies on for proper functioning. Things are broken down into increasing
46 We'll make the assumption below that the symbol is "mcount" just to keep things
74 typically the bare minimum with checking things before returning. That also
130 things.
185 be able to skimp on things saved/restored (usually just registers used to pass
235 You need very few things to get the syscalls tracing in an arch.
345 patching multiple things. First, only functions that we actually want to trace
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | ftrace-design.rst | 15 code relies on for proper functioning. Things are broken down into increasing
46 We'll make the assumption below that the symbol is "mcount" just to keep things
74 typically the bare minimum with checking things before returning. That also
130 things.
185 be able to skimp on things saved/restored (usually just registers used to pass
235 You need very few things to get the syscalls tracing in an arch.
345 patching multiple things. First, only functions that we actually want to trace
|
| /kernel/linux/linux-6.6/arch/x86/include/uapi/asm/ |
| D | debugreg.h | 14 /* Define a few things for the status register. We can use this to determine
50 /* Now define a bunch of things for manipulating the control register.
84 /* The second byte to the control register has a few special things.
|
| /kernel/linux/linux-6.6/Documentation/gpu/amdgpu/ |
| D | driver-core.rst | 17 the SoC itself rather than specific IPs. E.g., things like GPU resets
24 their interface to interact with those common components. For things
62 various things including paging and GPU page table updates. It's also
105 SoC and for things like init/fini/suspend/resume, more or less just
|
| /kernel/linux/linux-5.10/arch/sparc/include/asm/ |
| D | pbm.h | 12 * To put things into perspective, consider sparc64 with a few PCI controllers.
34 /* Now things for the actual PCI bus probes. */
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | mfd.txt | 10 silicon) that handles analog drivers for things like audio amplifiers, LED
11 drivers, level shifters, PHY (physical interfaces to things like USB or
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | mfd.txt | 10 silicon) that handles analog drivers for things like audio amplifiers, LED
11 drivers, level shifters, PHY (physical interfaces to things like USB or
|
| /kernel/linux/linux-6.6/arch/sparc/include/asm/ |
| D | pbm.h | 12 * To put things into perspective, consider sparc64 with a few PCI controllers.
34 /* Now things for the actual PCI bus probes. */
|
| /kernel/linux/linux-6.6/Documentation/security/ |
| D | self-protection.rst | 53 temporary exceptions to this rule to support things like instruction
117 things like compat, user namespaces, BPF creation, and perf limited only
159 the function returns. Other defenses include things like shadow stacks.
207 It should be noted that things like the stack canary discussed earlier
212 Blinding literal values for things like JITs, where the executable
270 addresses or other sensitive things like canary values).
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| D | self-protection.rst | 53 temporary exceptions to this rule to support things like instruction
118 things like compat, user namespaces, BPF creation, and perf limited only
160 the function returns. Other defenses include things like shadow stacks.
208 It should be noted that things like the stack canary discussed earlier
213 Blinding literal values for things like JITs, where the executable
271 addresses or other sensitive things like canary values).
|
| /kernel/linux/linux-5.10/arch/x86/platform/efi/ |
| D | efi_thunk_64.S | 9 * has been called. This simplifies things considerably as compared with
16 * 64-bit virtual address space. Things like the stack and instruction
|
| /kernel/linux/linux-5.10/drivers/misc/echo/ |
| D | echo.h | 40 things like modem line equalisers and line echo cancellers. There it works very
42 very poorly for things like speech echo cancellation, where the signal level
88 and the environment is not, things will be OK. Clearly, it is easy to tell when
|
| /kernel/linux/linux-6.6/drivers/misc/echo/ |
| D | echo.h | 40 things like modem line equalisers and line echo cancellers. There it works very
42 very poorly for things like speech echo cancellation, where the signal level
88 and the environment is not, things will be OK. Clearly, it is easy to tell when
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/kunit/ |
| D | faq.rst | 70 Unfortunately, there are a number of things which can break, but here are some
71 things to try.
91 enable/disable things with ``make ARCH=um menuconfig`` or similar, and then
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/kunit/ |
| D | faq.rst | 68 Unfortunately, there are a number of things which can break, but here are some
69 things to try.
89 enable/disable things with ``make ARCH=um menuconfig`` or similar, and then
|
12345678910>>...179