Searched full:things (Results 1 – 25 of 1646) sorted by relevance
12345678910>>...66
| /Linux-v5.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 */
|
| D | s2ram.rst | 23 way to debug these things, and it's actually pretty powerful (but
42 holding the power button down, and look at the dmesg output for things
|
| /Linux-v5.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
|
| /Linux-v5.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 …]
|
| D | management-style.rst | 57 needs to do is to turn the big and painful ones into small things where
71 things that can't be undone. Don't get ushered into a corner from which
219 Things will go wrong, and people want somebody to blame. Tag, you're it.
242 5) Things to avoid
257 Similarly, don't be too polite or subtle about things. Politeness easily
|
| /Linux-v5.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.
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.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. */
|
| /Linux-v5.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
|
| /Linux-v5.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).
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.10/drivers/gpu/drm/msm/disp/mdp5/ |
| D | mdp5_smp.h | 39 * 1) in _prepare_commit() we configure things (via read-modify-write)
42 * 2) in _complete_commit(), after vblank/etc, we clear things for the
|
| /Linux-v5.10/lib/kunit/ |
| D | kunit-example-test.c | 24 * This is an EXPECTATION; it is how KUnit tests things. When you want in example_simple_test()
64 * Often it is desirable to run some function which will set up things which
|
| /Linux-v5.10/Documentation/usb/ |
| D | gadget_multi.rst | 28 As one might expect, things one need to do very from system to system.
72 Things are harder with RDNIS and CDC ACM.
107 things don't work as intended before realising Windows have cached
|
| /Linux-v5.10/Documentation/sound/soc/ |
| D | jack.rst | 18 This is done by splitting the jacks up into three things working
56 update and the set of things to report when the jack is connected.
|
| /Linux-v5.10/drivers/soc/rockchip/ |
| D | io-domain.c | 155 /* if no VCCIO6 supply we should leave things alone */ in px30_iodomain_init()
174 /* if no flash supply we should leave things alone */ in rk3288_iodomain_init()
193 /* if no vccio2 supply we should leave things alone */ in rk3328_iodomain_init()
212 /* if no flash supply we should leave things alone */ in rk3368_iodomain_init()
231 /* if no pmu io supply we should leave things alone */ in rk3399_pmu_iodomain_init()
|
| /Linux-v5.10/Documentation/ABI/ |
| D | README | 54 with userspace developers to ensure that things do not
69 How things move between levels:
|
| /Linux-v5.10/Documentation/x86/ |
| D | tlb.rst | 19 Which method to do depends on a few things:
36 There is obviously no way the kernel can know all these things,
|
| /Linux-v5.10/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 17 (*) Things to avoid.
147 Things to Avoid
150 Do not mount other things within the cache as this will cause problems. The
166 Do not chmod files in the cache. The module creates things with minimal
193 disk space or files is permitted until culling has raised things above
263 they may also contain things like '/' and NUL characters, and so they may not
|
| /Linux-v5.10/lib/ |
| D | test_linear_ranges.c | 12 /* First things first. I deeply dislike unit-tests. I have seen all the hell
19 * coverage" - measured as line coverage. And that is one of the worst things
50 * or test more or less obvious things - but I want to see the main logic is
|
| /Linux-v5.10/arch/arm/nwfpe/ |
| D | ChangeLog | 26 and needs various things to be re-worked so that we won't
48 user_fp is smaller. This meant that the FPE scribbled on things
|
12345678910>>...66
