| /linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A 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>
|
| H A 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 …]
|
| H A D | sysfs-bus-event_source-devices-vpa-dtl | 3 Contact: Linux on PowerPC Developer List <linuxppc-dev at lists.ozlabs.org>
20 Contact: Linux on PowerPC Developer List <linuxppc-dev at lists.ozlabs.org>
|
| H A D | sysfs-driver-chromeos-acpi | 23 2 Developer.
39 32 Developer switch was enabled.
77 2 Developer mode switch.
|
| /linux/LICENSES/dual/ |
| H A 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 …]
|
| H A 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/Documentation/process/ |
| H A 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,
|
| H A 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
|
| H A D | security-bugs.rst | 139 Developer One <dev1@example.com> (maintainer:example driver)
140 Developer Two <dev2@example.org> (maintainer:example driver)
147 Developer One <dev1@example.com> (maintainer:example subsystem)
148 Developer Two <dev2@example.org> (maintainer:example subsystem)
149 Developer Three <dev3@example.com> (maintainer:example subsystem [GENERAL])
150 Developer Four <dev4@example.org> (maintainer:example subsystem [GENERAL])
|
| H A D | coding-assistants.rst | 31 Signed-off-by and Developer Certificate of Origin
35 certify the Developer Certificate of Origin (DCO). The human submitter
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | rsb.rst | 30 be one. So when the next CVE comes along, a kernel developer can
226 …ch Target Injection Mitigation <https://www.intel.com/content/www/us/en/developer/articles/technic…
238 …VE-2022-26373 / INTEL-SA-00706 <https://www.intel.com/content/www/us/en/developer/articles/technic…
242 … Branch Restricted Speculation <https://www.intel.com/content/www/us/en/developer/articles/technic…
246 … Branch Restricted Speculation <https://www.intel.com/content/www/us/en/developer/articles/technic…
248 …VE-2022-26373 / INTEL-SA-00706 <https://www.intel.com/content/www/us/en/developer/articles/technic…
258 …VE-2022-28693 / INTEL-SA-00702 <https://www.intel.com/content/www/us/en/developer/articles/technic…
260 …rect Branch Predictor Barrier' <https://www.intel.com/content/www/us/en/developer/articles/technic…
262 …VE-2022-28693 / INTEL-SA-00702 <https://www.intel.com/content/www/us/en/developer/articles/technic…
266 …CVE-2022-0002 / INTEL-SA-00598 <https://www.intel.com/content/www/us/en/developer/articles/technic…
[all …]
|
| /linux/Documentation/hwmon/ |
| H A 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:
|
| H A 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/Documentation/translations/zh_CN/maintainer/ |
| H A D | modifying-patches.rst | 24 Signed-off-by: Random J Developer <random@developer.example.org>
|
| /linux/Documentation/translations/ja_JP/process/ |
| H A D | submitting-patches.rst | 418 作業への署名 - Developer's Certificate of Origin
432 以下に示す英語原文の Developer's Certificate of Origin 1.1 です。
438 Developer's Certificate of Origin 1.1
466 Signed-off-by: Random J Developer <random@developer.example.org>
|
| /linux/security/smack/ |
| H A D | Kconfig | 26 rules. The developer can use the information to
28 may be inappropriate. The developer can reduce the
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A 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/Documentation/arch/arm/ |
| H A 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/>
|
| H A 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/Documentation/maintainer/ |
| H A D | modifying-patches.rst | 19 Signed-off-by: Random J Developer <random@developer.example.org>
|
| /linux/Documentation/netlabel/ |
| H A 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/ |
| H A D | README | 33 * New Kernel Developer: Getting started with kernel development
47 New Kernel Developer
158 and the Developer Certificate of Origin that all AI tools must comply with.
|
| /linux/Documentation/translations/pt_BR/process/ |
| H A D | security-bugs.rst | 145 Developer One <dev1@example.com> (maintainer:example driver)
146 Developer Two <dev2@example.org> (maintainer:example driver)
153 Developer One <dev1@example.com> (maintainer:example subsystem)
154 Developer Two <dev2@example.org> (maintainer:example subsystem)
155 Developer Three <dev3@example.com> (maintainer:example subsystem [GENERAL])
156 Developer Four <dev4@example.org> (maintainer:example subsystem [GENERAL])
|
| /linux/Documentation/ABI/ |
| H A D | README | 14 This directory documents the interfaces that the developer has
84 It's up to the developer to place their interfaces in the category they
|