Searched full:developer (Results 1 – 25 of 419) sorted by relevance
12345678910>>...17
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-ipmi | 4 Contact: openipmi-developer@lists.sourceforge.net
12 Contact: openipmi-developer@lists.sourceforge.net
23 Contact: openipmi-developer@lists.sourceforge.net
33 Contact: openipmi-developer@lists.sourceforge.net
42 Contact: openipmi-developer@lists.sourceforge.net
53 Contact: openipmi-developer@lists.sourceforge.net
63 Contact: openipmi-developer@lists.sourceforge.net
71 Contact: openipmi-developer@lists.sourceforge.net
81 Contact: openipmi-developer@lists.sourceforge.net
94 Contact: openipmi-developer@lists.sourceforge.net
[all …]
|
| D | sysfs-bus-event_source-devices-hv_24x7 | 3 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
28 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
38 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
45 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
52 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
59 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
66 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
73 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
80 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
91 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
|
| D | sysfs-bus-event_source-devices-hv_gpci | 3 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
34 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
44 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
51 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
58 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
65 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
72 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
79 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
86 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
118 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
[all …]
|
| D | sysfs-driver-chromeos-acpi | 23 2 Developer.
39 32 Developer switch was enabled.
77 2 Developer mode switch.
|
| /linux-6.12.1/LICENSES/dual/ |
| D | CDDL-1.0 | 35 1.5. "Initial Developer" means the individual or entity that first
86 2.1. The Initial Developer Grant.
89 to third party intellectual property claims, the Initial Developer
94 trademark) Licensable by Initial Developer, to use,
106 effective on the date Initial Developer first distributes
186 the Initial Developer.
196 on behalf of the Initial Developer or any Contributor. You must
199 agree to indemnify the Initial Developer and every Contributor for
200 any liability incurred by the Initial Developer or such Contributor
215 License are offered by You alone, not by the Initial Developer or
[all …]
|
| D | MPL-1.1 | 42 1.6. "Initial Developer" means the individual or entity identified
43 as the Initial Developer in the Source Code notice required by Exhibit
97 2.1. The Initial Developer Grant.
98 The Initial Developer hereby grants You a world-wide, royalty-free,
102 trademark) Licensable by Initial Developer to use, reproduce,
113 effective on the date Initial Developer first distributes
189 Code provided by the Initial Developer and including the name of the
190 Initial Developer in (a) the Source Code, and (b) in any notice in an
236 Developer or any Contributor. You must make it absolutely clear than
239 Developer and every Contributor for any liability incurred by the
[all …]
|
| /linux-6.12.1/Documentation/process/ |
| D | researcher-guidelines.rst | 24 generally, ethics in technology, and research of developer communities
29 * `Developer and Researcher Views on the Ethics of Experiments on Open-Source Projects <https://arx…
42 Active research on developer behavior, however, must be done with the
53 because every developer benefits from their participation, even working
64 As an alternative, researchers should consider attending developer events,
78 to. Such communication can be damaging to the developer (e.g. draining
80 the entire developer community's trust in the contributor (and the
90 When engaging with the developer community, sending a patch has
161 developer familiar with Linux contribution, especially within your own
168 related to this document and the developer community's expectations,
|
| D | 2.Process.rst | 143 Patches do not go directly from the developer's keyboard into the mainline
148 and controversial changes, go on for years. Much developer frustration
191 the developer be responsive to these and fix any issues which arise.
196 - Long-term maintenance. While it is certainly possible for a developer
200 problems caused by API changes. But the original developer should
216 where no single developer could possibly inspect and select every patch
222 devices, etc. Most subsystems have a designated maintainer, a developer
|
| D | index.rst | 12 So you want to be a Linux kernel developer? Welcome! While there is a lot
52 Policy guides and developer statements
|
| D | 1.Intro.rst | 92 experience behind it. A developer who does not understand the kernel
136 works, for the developer and for the user. Incorporation into the
149 result of a simple rule requiring any developer who makes an API change
159 the mainline. No matter how strong the original developer's skills are,
|
| D | 5.Posting.rst | 112 - Do not overdo it, though. One developer once posted a set of edits
237 - Signed-off-by: this is a developer's certification that he or she has
239 agreement to the Developer's Certificate of Origin, the full text of
250 - Acked-by: indicates an agreement by another developer (often a
257 - Reviewed-by: the named developer has reviewed the patch for correctness;
|
| /linux-6.12.1/Documentation/devicetree/bindings/arm/ |
| D | tegra.yaml | 180 - description: Jetson TX2 Developer Kit
184 - description: Jetson TX2 NX Developer Kit
188 - description: Jetson AGX Xavier Developer Kit
200 - description: Jetson Xavier NX Developer Kit
204 - description: Jetson Xavier NX Developer Kit (eMMC)
215 - description: Jetson AGX Orin Developer Kit
229 - description: Jetson Orin NX Engineering Reference Developer Kit
238 - description: Jetson Orin Nano Developer Kit
|
| /linux-6.12.1/Documentation/hwmon/ |
| D | k10temp.rst | 41 BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h Processors:
45 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 11h Processors:
49 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 12h Processors:
53 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 14h Models 00h-0Fh Processors:
|
| D | fam15h_power.rst | 16 - BIOS and Kernel Developer's Guide (BKDG) For AMD Family 15h Processors
17 - BIOS and Kernel Developer's Guide (BKDG) For AMD Family 16h Processors
|
| /linux-6.12.1/Documentation/filesystems/xfs/ |
| D | xfs-maintainer-entry-profile.rst | 36 - **Developer**: Someone who is familiar with the XFS codebase enough to
42 - **Senior Developer**: A developer who is very familiar with at least
51 - **Reviewer**: Someone (most likely also a developer) who reads code
82 If a developer and a reviewer fail to reach a resolution on some point,
|
| /linux-6.12.1/include/linux/ |
| D | kernel.h | 248 * This function allows a kernel developer to debug fast path sections
250 * printk like tracing in the code, a developer can quickly see
253 * This is intended as a debugging tool for the developer only.
308 * paths that a developer wants the least amount of "Heisenbug" effects,
311 * This function allows a kernel developer to debug fast path sections
313 * printk like tracing in the code, a developer can quickly see
316 * This is intended as a debugging tool for the developer only.
|
| /linux-6.12.1/Documentation/translations/zh_CN/maintainer/ |
| D | modifying-patches.rst | 24 Signed-off-by: Random J Developer <random@developer.example.org>
|
| /linux-6.12.1/security/smack/ |
| D | Kconfig | 26 rules. The developer can use the information to
28 may be inappropriate. The developer can reduce the
|
| /linux-6.12.1/Documentation/devicetree/bindings/mfd/ |
| D | arm,dev-platforms-syscon.yaml | 7 title: Arm Ltd Developer Platforms System Controllers
13 The Arm Ltd Integrator, Realview, and Versatile families of developer
|
| /linux-6.12.1/Documentation/arch/arm/ |
| D | arm.rst | 51 http://www.arm.linux.org.uk/developer/patches/info.php Always include some
56 http://www.arm.linux.org.uk/developer/
172 <http://www.arm.linux.org.uk/developer/machines/>
205 <http://www.arm.linux.org.uk/developer/machines/>
|
| D | ixp4xx.rst | 21 http://developer.intel.com/design/network/products/npfamily/ixp4xx.htm
48 http://developer.intel.com/design/network/products/npfamily/ixp425.htm
57 Open Source Developer's Guide for using uClinux and the Intel libraries
|
| /linux-6.12.1/Documentation/maintainer/ |
| D | modifying-patches.rst | 19 Signed-off-by: Random J Developer <random@developer.example.org>
|
| /linux-6.12.1/Documentation/netlabel/ |
| D | lsm_interface.rst | 27 configuration. It is up to the LSM developer to translate the NetLabel
34 These are the functions which allow the LSM developer to manipulate the labels
|
| /linux-6.12.1/Documentation/ABI/ |
| D | README | 13 This directory documents the interfaces that the developer has
81 It's up to the developer to place their interfaces in the category they
|
| /linux-6.12.1/Documentation/translations/ja_JP/ |
| D | SubmittingPatches | 330 Signed-off-by: Random J Developer <random@developer.example.org>
352 Signed-off-by: Random J Developer <random@developer.example.org>
|
12345678910>>...17