| /linux/Documentation/power/ |
| H A 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 */
|
| /linux/Documentation/process/ |
| H A 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
|
| H A D | howto.rst | 56 of doing things.
129 not have a stable API within the kernel, including things like:
384 you want to bring up, before you post it to the list. A lot of things
447 again, sometimes things get lost in the huge volume.
464 of a dozen things you should correct. This does **not** imply that your
474 development environments. Here are a list of things that you can try to
477 Good things to say regarding your proposed changes:
486 Bad things you should avoid saying:
531 The reasons for breaking things up are the following:
601 All of these things are sometimes very hard to do. It can take years to
[all …]
|
| H A 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/Documentation/driver-api/ |
| H A 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/Documentation/trace/ |
| H A 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
223 You need very few things to get the syscalls tracing in an arch.
329 patching multiple things. First, only functions that we actually want to trace
|
| /linux/arch/x86/include/uapi/asm/ |
| H A 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.
|
| /linux/Documentation/security/ |
| H A 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).
|
| /linux/arch/sparc/include/asm/ |
| H A 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/Documentation/devicetree/bindings/mfd/ |
| H A 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/include/uapi/linux/ |
| H A D | rfkill.h | 143 * accessed them, but things should've continued to work.
147 * did all kinds of fun things not in line with this scheme:
155 * things to no longer work correctly on old and new kernels.
|
| /linux/Documentation/dev-tools/kunit/ |
| H A 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
|
| /linux/drivers/soc/rockchip/ |
| H A D | io-domain.c | 203 /* if no VCCIO6 supply we should leave things alone */ in px30_iodomain_init()
222 /* if no flash supply we should leave things alone */ in rk3288_iodomain_init()
241 /* if no vccio3 supply we should leave things alone */ in rk3308_iodomain_init()
260 /* if no vccio2 supply we should leave things alone */ in rk3328_iodomain_init()
279 /* if no flash supply we should leave things alone */ in rk3368_iodomain_init()
298 /* if no pmu io supply we should leave things alone */ in rk3399_pmu_iodomain_init()
|
| /linux/drivers/android/binder/ |
| H A D | rust_binder_internal.h | 5 * these are type definitions used only by binderfs or things that Rust Binder
8 * It does not include things exported by binderfs to Rust Binder since this
|
| /linux/Documentation/usb/ |
| H A 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/arch/parisc/lib/ |
| H A D | io.c | 57 * of the inw() breaks things.
129 * of the inl() breaks things.
227 * outw() breaks things.
299 * just using the inlined version of the outl() breaks things.
|
| /linux/include/linux/ |
| H A D | ipmi.h | 142 * things it takes to determine your address (if not the BMC) and set
228 * things with the interface. It will still respond to attentions and
230 * will not automatcially check for flags, events, or things of that
348 * For things that must send messages at panic time, like the IPMI watchdog
|
| /linux/Documentation/translations/zh_TW/cpu-freq/ |
| H A D | core.rst | 97 /* Do things */
101 /* Do other things */
|
| /linux/drivers/gpu/drm/msm/disp/mdp5/ |
| H A 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/Documentation/translations/zh_CN/cpu-freq/ |
| H A D | core.rst | 97 /* Do things */
101 /* Do other things */
|
| /linux/arch/x86/platform/efi/ |
| H A 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/Documentation/sound/soc/ |
| H A 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/tools/verification/rv/src/ |
| H A D | trace.c | 87 * things required for the tracing, such as the local events and
114 * things such as the priority of the tracer's threads. in trace_instance_init()
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 62 Note: this section covers a few more aspects than the TL;DR and does things in
145 issue. Always mention a few things: the latest kernel version you installed
164 report your results. Send friendly reminders if things stall. And try to
251 work, so that's just how things are for now.
450 Reminder, you are dealing with computers, which sometimes do unexpected things,
507 three things:
1008 is, someone might help you to get things going. Also be aware this is just one
1072 issue. Always mention a few things: the latest kernel version you installed
1090 things specific to the Linux kernel.
1100 Things each report should mention
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | uncore-interconnect.json | 864 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
873 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
883 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
893 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
903 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
913 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
923 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
933 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
943 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
953 …QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting tr…
[all …]
|