Searched full:them (Results 1 – 25 of 1059) sorted by relevance
12345678910>>...43
| /Documentation/admin-guide/mm/ |
| D | swap_numa.rst | 17 to be swapped on. Simply swapping them on by doing::
24 that the order of them being swapped on doesn't matter.
29 The way to swap them on is the same as above::
38 Then node 0 will use them in the order of::
44 node 1 will use them in the order of::
48 node 2 will use them in the order of::
55 node 3 will use them in the order of::
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 6 Good development is like gardening, and codebases are our gardens. Tend to them
32 are logically impossible. (Or, make them debug mode assertions if they're
47 means that you can run them in only a few places in the checked in version, but
49 quickly shotgun them everywhere to find the codepath that broke the invariant.
71 percpu data structures among them. Don't let things stay hidden.
76 Pretty printers are wonderful, because they compose and you can use them
88 the issue. It's worth putting effort into them.
118 Users notice all sorts of interesting things, and by just talking to them and
119 interacting with them you can benefit from their experience.
134 Expect to throw a lot of things away, or leave them half finished for later.
|
| /Documentation/hwmon/ |
| D | vexpress.rst | 28 from a wide range of boards, each of them containing (apart of the main
33 temperature and power usage. Some of them also calculate consumed energy
40 Tree passed to the kernel. Details of the DT binding for them can be found
|
| D | userspace-tools.rst | 19 setup monitoring limits etc. You can get them on their homepage
32 3) load them and run "sensors" command, you should see some results.
|
| /Documentation/driver-api/ |
| D | isa.rst | 22 to the driver creating them because it might want to drive them, meaning
54 them in at all. The id is the only thing we ever want other then the
60 of the old .probe in .match, which would only keep them registered after
78 loops over the passed in ndev creating devices and registering them.
79 This causes the bus match method to be called for them, which is::
|
| /Documentation/i2c/ |
| D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
21 hardware doesn't support them (SMBus doesn't require 10-bit address
33 needs them to be fixed.
|
| /Documentation/ |
| D | Kconfig | 21 have errors that would break them for being parsed by
22 scripts/get_abi.pl. Add a check to verify them.
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 9 errors or security problems are found in them.
17 developers can easily notify them if any changes occur.
|
| /Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 32 cannot be implemented without platform support and the difference between them
34 resume hooks that need to be provided by the platform driver to make them
53 That allows them to prepare for the change of the system state and to clean
84 accessed in more than two of them.
97 transition of the system is started when one of them signals an event.
102 into the deepest available idle state. While doing that, each of them
114 interrupt that woke up one of them comes from an IRQ that has been armed for
144 accessed in more than two of them.
161 "notification type" parameter value is passed to them.
187 when all CPUs in them are in sufficiently deep idle states and all I/O
|
| D | cpuidle.rst | 23 Since part of the processor hardware is not used in idle states, entering them
39 (program) from memory and executing them, but it need not work this way
49 work physically in parallel with each other, so if each of them executes only
63 instructions from multiple locations in memory and execute them in the same time
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
81 *idle* by the Linux kernel when there are no tasks to run on them except for the
99 to allow them to make some progress over time.]
163 ``ladder`` and ``haltpoll``. Which of them is used by default depends on the
179 decision on which one of them to use has to be made early (on Intel platforms
194 allow them to make reasonable progress in a given time frame is to make them
[all …]
|
| D | strategies.rst | 15 One of them is based on using global low-power states of the whole system in
33 allowing them to process data and to be accessed by software. In turn, if they
39 draw (or maximum energy usage) of it. If all of them are inactive, the system
|
| /Documentation/devicetree/bindings/pwm/ |
| D | clk-pwm.yaml | 14 (e.g. by muxing them to GPIO pins)
15 It's often possible to control duty-cycle of such clocks which makes them
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 18 but not explicitly acknowledged them to firmware and
24 entries, read them out and acknowledge them.
|
| /Documentation/input/ |
| D | gamepad.rst | 45 differently labeled on most devices so we define them as NORTH,
57 Analog-sticks may also provide a digital button if you press them.
60 Not all devices provide them, but the upper buttons are normally named
74 Legacy drivers often don't comply to these rules. As we cannot change them
76 user-space yourself. Some of them might also provide module-options that
85 and one analog stick. It reports them as if it were a gamepad with only one
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_build.rst | 21 To build only static libbpf.a library in directory build/ and install them
31 dependency installed in /build/root/ and install them together with libbpf
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 28 information from the device objects represented by them and populating them with
29 appropriate data, but some of them require additional handling after they have
56 to match a scan handler against each of them using the ids arrays of the
|
| /Documentation/process/ |
| D | management-style.rst | 47 competent to make that decision for them.
114 sure as hell shouldn't encourage them by promising them that what they
115 work on will be included. Make them at least think twice before they
150 is fairly easy, and un-alienating them is hard. Thus "alienating"
193 Some people react badly to smart people. Others take advantage of them.
196 Suck up to them, because they are the people who will make your job
212 are doing something irreversible when you **do** prod them in some
229 Then make the developer who really screwed up (if you can find them) know
287 by trying to keep up with everybody else and running after them as fast
|
| /Documentation/trace/coresight/ |
| D | coresight-dummy.rst | 15 platforms. For these devices, a dummy driver is needed to register them as
19 disabling them. It also provides the Coresight dummy sink/source paths for
|
| /Documentation/timers/ |
| D | hrtimers.rst | 49 them becomes necessary. Thus the users of these timeouts can accept
52 Accurate timing for them is not a core purpose - in fact most of the
53 timeout values used are ad-hoc. For them it is at most a necessary
109 time-changing code had to fix them up one by one, and all of them had to
122 1:1 mapping between them on the algorithmic level, and thus no real
|
| D | no_hz.rst | 110 task implies also omitting them for idle CPUs.
116 it allows them to improve their worst-case response times by the maximum
162 all of them over time. Adaptive-tick mode may prevent this
195 scheduler will decide where to run them, which might or might not be
196 where you want them to run.
229 dyntick-idle mode, an option that most of them take. However,
282 simply offloading RCU callbacks from all CPUs and pinning them
283 where you want them whenever you want them pinned.
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| /Documentation/core-api/ |
| D | boot-time-mm.rst | 34 macros. Some of them are actually internal, but since they are
35 documented it would be silly to omit them. Besides, reading the
|
| /Documentation/devicetree/bindings/leds/ |
| D | rohm,bd2606mvv.yaml | 14 drive 6 separate lines. Each of them can be individually switched on and off,
15 but the brightness setting is shared between pairs of them.
|
| /Documentation/ABI/ |
| D | README | 16 them will be guaranteed for at least 2 years. Most interfaces
25 errors or security problems are found in them. Userspace
31 notify them if any changes occur (see the description of the
|
| /Documentation/livepatch/ |
| D | cumulative-patches.rst | 15 from all older livepatches and completely replace them in one transition.
97 must create their own rules how to pass them from one cumulative
99 them in module_exit() functions.
|
12345678910>>...43