Searched full:their (Results 1 – 25 of 871) sorted by relevance
12345678910>>...35
| /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/networking/ |
| D | ipv6.txt | 21 The possible values and their effects are:
43 The possible values and their effects are:
61 The possible values and their effects are:
|
| /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
|
| D | sysfs-class-bdi | 14 non-block filesystems which provide their own BDI, such as NFS
24 filesystems which do not provide their own BDI.
|
| /Documentation/devicetree/bindings/nds32/ |
| D | andestech-boards | 23 simply attach their IP on one of the system buses together with certain glue
26 system performance of their applications and track bugs of their designs
|
| /Documentation/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/admin-guide/namespaces/ |
| D | resource-control.rst | 8 enabled in a kernel for people who don't trust their users or their
|
| /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/interrupt-controller/ |
| D | qcom,pdc.txt | 11 wakeup capabilities of their device interrupts routed through the PDC, must
12 specify PDC as their interrupt controller and request the PDC port associated
51 and their hwirq mapping.
|
| /Documentation/process/ |
| 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.
56 making. Do not let their form of expression or your own pride keep that
60 thank them, and describe how you will answer their questions.
122 default. Subsystem trees typically feed linux-next as well, making their
154 how many people will build your code into their kernels. And, of course,
179 development community remembers developers who lose interest in their code
|
| D | stable-api-nonsense.rst | 47 that describes kernel drivers that do not have their source code
125 running almost all USB devices at their maximum speed possible.
132 which have had to maintain their older USB interfaces over time. This
143 their work on their own time, asking programmers to do extra work for no
203 Robert Love, and Nishanth Aravamudan for their review and comments on
|
| D | kernel-driver-statement.rst | 15 model and shut their users off from the expertise of the Linux
16 community. Vendors that provide closed-source kernel modules force their
20 adopt a policy of supporting their customers on Linux with open-source
|
| /Documentation/ABI/stable/ |
| D | vdso | 9 within their rights to crash.) In addition, if you pass a bad
28 that it is correct for their architecture.)
|
| /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/filesystems/ |
| D | devpts.txt | 2 and their indicies allocated in one mount are independent from ptys
3 and their indicies in all other mounts.
|
| /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/mtd/partitions/ |
| D | brcm,bcm947xx-cfe-partitions.txt | 5 home routers. Their BCM947xx boards using CFE bootloader have several partitions
6 without any on-flash partition table. On some devices their sizes and/or
|
| /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/scsi/ |
| D | BusLogic.txt | 21 collection of bus architectures by virtue of their MultiMaster ASIC technology.
35 analogous to the firmware on the MultiMaster Host Adapters. Thanks to their
45 tune driver performance and error recovery to their particular needs.
58 Mylex has been an excellent company to work with and I highly recommend their
60 opportunity to become a beta test site for their latest MultiMaster product,
63 Mylex received a degree and kind of testing that their own testing group cannot
67 directly with their technical staff, to understand more about the internal
68 workings of their products, and in turn to educate them about the needs and
76 problem and are running Linux, they will not tell you that your use of their
77 products is unsupported. Their latest product marketing literature even states
[all …]
|
| /Documentation/fb/ |
| D | tridentfb.rst | 10 those from the TGUI series 9440/96XX and with Cyber in their names
11 those from the Image series and with Cyber in their names
12 those with Blade in their names (Blade3D,CyberBlade...)
|
| /Documentation/devicetree/bindings/reset/ |
| D | ti-syscon-reset.txt | 5 to clock and power control for their functionality. The reset control is
9 allow multiple entities to access their relevant registers in the common
52 in addition to their own properties.
|
| /Documentation/admin-guide/cifs/ |
| D | authors.rst | 21 Newbigin and others for their work on the Linux smbfs module. Thanks to
23 Workgroup for their work specifying this highly complex protocol and finally
24 thanks to the Samba team for their technical advice and encouragement.
|
| /Documentation/admin-guide/device-mapper/ |
| D | kcopyd.rst | 10 to set aside for their copy jobs. This is done with a call to
43 When a user is done with all their copy jobs, they should call
|
12345678910>>...35