Searched full:their (Results 1 – 25 of 1081) sorted by relevance
12345678910>>...44
| /Documentation/process/ |
| D | contribution-maturity-model.rst | 16 maintainers as part of their job, so they can grow into becoming
29 The TAB urges organizations to continuously evaluate their Open Source
34 publish their evaluations and plans to improve their engagement with the
48 kernel, either as part of their job responsibilities or on their own
55 part of their job responsibilities.
57 conferences as a part of their job.
65 authored by engineers from other companies) as part of their job
72 * Organizations will regularly report metrics of their open source
91 * Software Engineers are encouraged to spend a portion of their work
|
| D | 1.Intro.rst | 10 and the kinds of frustrations that developers and their employers can
63 vendors want to ensure that Linux supports their products well, making
67 other software vendors who base their products on Linux have a clear
70 better suit their needs.
121 learning how to work with the kernel community and get their code into the
169 to implement changes which make the kernel work better for their needs.
196 a result, their distribution is a violation of the GNU General Public
212 will have to upgrade your module separately every time they upgrade their
249 be obtained (or their code removed from the kernel). So, in particular,
256 off" on their code, stating that the code can be distributed with the
|
| D | 6.Followthrough.rst | 9 developers can make is to conclude that their work is now done. In truth,
47 - Similarly, code reviewers are not trying to promote their employers'
49 be working on the kernel years from now, but they understand that their
52 trying to create discomfort for their employers' competitors.
63 making. Do not let their form of expression or your own pride keep that
67 thank them, and describe how you will answer their questions.
129 default. Subsystem trees typically feed linux-next as well, making their
161 how many people will build your code into their kernels. And, of course,
186 development community remembers developers who lose interest in their code
|
| D | embargoed-hardware-issues.rst | 66 confidentiality by their employment contract. Linux Foundation IT
149 via their employer, they cannot enter individual non-disclosure agreements
150 in their role as Linux kernel developers. They will, however, agree to
209 and the disclosing party is requested to acknowledge their participation.
229 To allow the affected silicon vendors to work with their internal teams and
237 have and maintain their own documented security process for any
238 patches shared with their response team that is consistent with
242 their industry partners and to their internal teams under the
265 required for all involved parties to develop, test, and prepare their
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | data-structure-v9.rst | 30 In this table, horizontally, devices can be accessed from resources by their
32 their volume number. Objects in the vertical direction are connected by double
33 linked lists. There are back pointers from peer_devices to their connections a
34 devices, and from connections and devices to their resource.
37 devices can be accessed by their minor device number via the drbd_devices idr.
41 devices and connections; their lifetime is determined by the lifetime of the
|
| /Documentation/scheduler/ |
| D | sched-eevdf.rst | 22 which helps with their responsiveness.
27 by sleeping briefly to reset their negative lag: when a task sleeps, it
29 lag to decay over VRT. Hence, long-sleeping tasks eventually have their lag
30 reset. Finally, tasks can preempt others if their VD is earlier, and tasks
|
| /Documentation/networking/ |
| D | ipv6.rst | 27 The possible values and their effects are:
49 The possible values and their effects are:
67 The possible values and their effects are:
|
| /Documentation/core-api/ |
| D | floating-point.rst | 28 ``linux/fpu.h``, as described below. Some other architectures implement their
41 Architectures are expected to define one or both of these variables in their
56 from files implementing FP code (those with their compilation flags adjusted as
75 Preemption may be disabled inside critical sections, so their size
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid-corsair | 6 where G-keys triggers their regular key codes. "HW" for
7 hardware playback mode where the G-keys play their macro
|
| /Documentation/arch/mips/ |
| D | ingenic-tcu.rst | 19 different clocks (pclk, ext, rtc), gated, and reclocked, through their TCSR register.
22 format in their register space.
44 - on older SoCs (JZ4740 and below), channel 0 and channel 1 have their
68 drivers access their registers through the same regmap.
|
| /Documentation/power/regulator/ |
| D | consumer.rst | 75 Some consumer drivers need to be able to dynamically change their supply
80 Consumers can control their supply voltage by calling::
106 Some consumer drivers need to be able to dynamically change their supply
111 Consumers can control their supply current limit by calling::
138 their supply regulator to be more efficient when the consumers operating state
145 Consumer drivers can request a change in their supply regulator operating mode
166 operating mode depending on their operating point. This can be achieved by
192 Regulators use the kernel notifier framework to send event to their interested
|
| /Documentation/usb/ |
| D | CREDITS | 48 - USAR Systems provided us with one of their excellent USB
55 - Thanks to Intel Corporation for their precious help.
64 - Due to their support to us, Keytronic can be sure that they
83 - Thanks to Y-E Data, Inc. for donating their FlashBuster-U
99 Logitech customers to enjoy support in their favorite
164 - All the people at the USB Implementors Forum for their
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | ubi-volume.yaml | 11 by their ID or their name, or both.
|
| /Documentation/admin-guide/namespaces/ |
| D | resource-control.rst | 8 enabled in a kernel for people who don't trust their users or their
|
| /Documentation/devicetree/bindings/regulator/ |
| D | maxim,max77802.yaml | 25 and their meaning is::
30 support changing their mode to Low Power Mode during suspend. These
43 LDOs supporting the regulator-initial-mode property and changing their
|
| /Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 44 ECR. (Developers may, of course, maintain their own Linux kernel trees
48 their own custom extensions. These custom extensions aren't required
58 (Implementers, may, of course, maintain their own Linux kernel trees containing
|
| /Documentation/networking/devlink/ |
| D | devlink-trap.rst | 31 The ``devlink-trap`` mechanism allows capable device drivers to register their
125 Such traps can be shared by multiple device drivers and their description must
185 routed and their destination IP is the loopback address (i.e., 127.0.0.0/8
190 routed and their source IP is multicast (i.e., 224.0.0.0/8 and ff::/8)
194 routed and their source IP is the loopback address (i.e., 127.0.0.0/8 and ::1/128)
198 routed and their IP header is corrupted: wrong checksum, wrong IP version
203 routed and their source IP is limited broadcast (i.e., 255.255.255.255/32)
207 be routed and their IPv6 multicast destination IP has a reserved scope
212 be routed and their IPv6 multicast destination IP has an interface-local scope
247 - Traps NVE packets that the device decided to drop because their overlay
[all …]
|
| /Documentation/bpf/libbpf/ |
| D | index.rst | 14 libbpf APIs and their usage. This will give you a solid foundation to start
28 All general BPF questions, including kernel functionality, libbpf APIs and their
|
| /Documentation/driver-api/ |
| D | regulator.rst | 37 can enable and disable their output and some can also control their
68 When requesting regulators consumers use symbolic names for their
92 Some consumer devices may need to be able to dynamically configure their
94 operating voltage for their cards. This may be done while the regulator
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 30 their DVFS state together, i.e. they share clock/voltage/current lines.
40 Their name isn't significant but their phandle can be used to reference an
55 to relate the values to their clocks or the order in which the clocks
71 relate the values to their power supplies or the order in which the supplies
98 values to their power supplies or the order in which the supplies need
113 values to their power supplies or the order in which the supplies need
|
| /Documentation/driver-api/pm/ |
| D | notifiers.rst | 19 For example, device drivers may want to upload firmware to their devices after
21 from their ``->resume()`` or ``->complete()`` callback routines (user land
67 They are defined in the usual way, but their last argument is meaningless (it is
|
| /Documentation/devicetree/bindings/access-controllers/ |
| D | access-controllers.yaml | 16 their responsibility (their domain) can be accesssed by which compartment. A
21 This device tree binding can be used to bind devices to their access
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | qcom,pdc.yaml | 21 wakeup capabilities of their device interrupts routed through the PDC, must
22 specify PDC as their interrupt controller and request the PDC port associated
75 and their hwirq mapping.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | max77620.txt | 16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
26 Optional subnodes and their properties:
64 and their child for FPS specific. The child node name for FPS are "fps0",
68 regulators, GPIOs and 32kHz clocks are provided in their respective
130 under their respective sub-system directories.
|
| /Documentation/ABI/stable/ |
| D | vdso | 17 within their rights to crash.) In addition, if you pass a bad
37 that it is correct for their architecture.
|
12345678910>>...44