| /linux/Documentation/process/ |
| H A D | 1.Intro.rst | 9 The rest of this section covers the scope of the kernel development process
14 influence the direction of kernel development. Code contributed to the
17 :ref:`development_process` introduces the development process, the kernel
19 the patch development, review, and merging cycle are covered. There is some
21 with kernel development are encouraged to track down and fix bugs as an
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
40 of the development process; this section offers a number of tips on how to
48 for more information on kernel development.
62 (and companies) wishing to participate in its development. Hardware
[all …]
|
| H A D | 2.Process.rst | 3 How the development process works
6 Linux kernel development in the early 1990's was a pretty loose affair,
10 processes to keep development happening smoothly. A solid understanding of
32 the leading edge of Linux kernel development; the kernel uses a
33 rolling development model which is continually integrating major changes.
36 merging of patches for each release. At the beginning of each development
38 deemed to be sufficiently stable (and which is accepted by the development
40 new development cycle (and all of the major changes) will be merged during
62 best thing to do is to wait for the next development cycle. (An occasional
73 As an example, here is how the 5.4 development cycle went (all dates in
[all …]
|
| H A D | howto.rst | 3 HOWTO do Linux kernel development
8 to work with the Linux kernel development community. It tries to not
29 kernel development. Assembly (any architecture) is not required unless
30 you plan to do low-level development for that architecture. Though they
50 existing development community. It is a diverse group of people, with
136 This document is crucial for understanding the Linux development
138 development on other Operating Systems.
148 for anyone new to kernel development (or anyone simply curious about
159 development. Please consult this list if you do not find what you
164 apply it to the different development branches of the kernel.
[all …]
|
| H A D | 3.Early-stage.rst | 6 When contemplating a Linux kernel development project, it can be tempting
41 entire kernel development process; one of them went back to an audio list
55 - and to discuss it with the development community before investing in the
58 So, when contemplating a kernel development project, one should obtain
74 When planning a kernel development project, it makes great sense to hold
95 Years of experience with the kernel development community have taught a
145 development project.
173 provide can help the development community provide useful input on the
201 of a kernel development project, the better off everybody involved will be.
208 need to keep development plans behind closed doors.
[all …]
|
| H A D | development-process.rst | 3 A guide to the Kernel Development Process
7 work with the development community with a minimum of frustration. It is
10 development (or, indeed, free software development in general). While
|
| H A D | embargoed-hardware-issues.rst | 92 community compliant development under embargo restrictions.
117 Due to the globally distributed nature of Linux kernel development,
146 development process.
161 participate in the mitigation development.
178 Mitigation development
184 Using a mailing list is close to the normal Linux development process and
188 The mailing list operates in the same way as normal Linux development.
192 development branch against the mainline kernel and backport branches for
200 Bringing in experts can happen at any time in the development process and
216 is disclosed and brought into the development process.
[all …]
|
| H A D | 8.Conclusion.rst | 6 There are numerous sources of information on Linux kernel development and
16 Various web sites discuss kernel development at all levels of detail. Your
30 There are a number of books on kernel development:
36 Linux Kernel Development (Robert Love).
71 the direction of kernel development, and more. It is a situation where
|
| H A D | 7.AdvancedTopics.rst | 6 At this point, hopefully, you have a handle on how the development process
9 regular part of the Linux kernel development process.
18 control enabled an immediate acceleration of the kernel development
29 fits into the kernel development process in particular. Developers who
61 of development can be separated into a separate "topic branch" and
64 development in any branch which you intend to ask others to pull from.
66 from development branches when they are in complete form and ready to go -
70 development history. An inconvenient patch (one which breaks bisection,
97 of the reasons why development should be done in private branches (which
|
| H A D | 6.Followthrough.rst | 14 room for improvement. The kernel development process recognizes this fact,
27 many developers, the most intimidating part of the kernel development
37 still be around and under development a decade from now.
105 kernel development community; he can often unjam a situation which seems to
130 contents visible to the development community as a whole. At this point,
186 development community remembers developers who lose interest in their code
|
| H A D | index.rst | 9 Working with the kernel development community
18 An introduction to how kernel development works
28 development-process
|
| /linux/arch/mips/generic/ |
| H A D | Kconfig | 28 development boards, which boot using a legacy boot protocol.
56 Enable this to include the FDT for the MIPS Boston development board
80 bool "Include FDT for Microsemi Ocelot development platforms"
83 Enable this to include the FDT for the Ocelot development platforms
88 bool "Include FDT for Microsemi Luton development platforms"
91 Enable this to include the FDT for the Luton development platforms
96 bool "Include FDT for Microsemi Jaguar2 development platforms"
99 Enable this to include the FDT for the Jaguar2 development platforms
104 bool "Include FDT for Microsemi Serval development platforms"
107 Enable this to include the FDT for the Serval development platforms
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 17 development history. Indeed, given the scale of the project, avoiding
42 Used properly, rebasing can yield a cleaner and clearer development
73 between release points; basing development on one of those points
97 Merging is a common operation in the kernel development process; the 5.1
98 development cycle included 1,126 merge commits - nearly 9% of the total.
128 branches. Failure to do so threatens the security of the development
145 sure that there are no conflicts with parallel development and generally
149 Why is that? Back merges will muddy the development history of your own
153 also obscure problems with the development process in your tree; they can
171 in the 5.1 development cycle) and has gotten quite good at conflict
[all …]
|
| H A D | feature-and-driver-maintainers.rst | 86 Open development
89 Discussions about user reported issues, and development of new code
91 It is common for development within a single company to be conducted
92 behind closed doors. However, development and discussions initiated
148 - (when development is contracted) works for a company which paid
149 for the development rather than the company which did the work
156 role in the development of the code, they should be moved to the CREDITS file.
|
| H A D | messy-diffstat.rst | 11 complicated development history will yield a massive diffstat containing a
20 A Git development history proceeds as a series of commits. In a simplified
21 manner, mainline kernel development looks like this::
46 consider a slightly more complex development history::
60 the ``git diff`` operation to use. The development culminating in cN
|
| /linux/Documentation/ |
| H A D | index.rst | 16 Working with the development community
19 The essential guides for interacting with the kernel's development
25 Development process <process/development-process>
29 All development-process docs <process/index>
46 Development tools and processes
56 Development tools <dev-tools/index>
|
| /linux/Documentation/usb/ |
| H A D | CREDITS | 38 of hardware, support, time and development (this is from the original
41 The following corporations have helped us in the development
77 - AVM GmbH Berlin is supporting the development of the Linux
111 converter products for development.
119 the driver development.
|
| /linux/Documentation/devicetree/bindings/arm/omap/ |
| H A D | omap.txt | 116 - DRA762 EVM: Software Development Board for DRA762
119 - DRA742 EVM: Software Development Board for DRA742
122 - DRA722 EVM: Software Development Board for DRA722
125 - DRA718 EVM: Software Development Board for DRA718
|
| /linux/Documentation/arch/arc/ |
| H A D | arc.rst | 17 Home for all development activities regarding open source projects for
50 SoC bringup and software development in general.
58 - Cross-compilation: process of compiling for ARC targets on a development
61 (hardware board or a simulator like QEMU) with complete development environment
|
| /linux/arch/arm/mach-sa1100/ |
| H A D | Kconfig | 33 Microprocessor Development Board (also known as the Assabet).
41 Microprocessor Development Board (Assabet) with the SA-1111
42 Development Board (Nepon).
|
| /linux/Documentation/devicetree/bindings/arm/ti/ |
| H A D | omap.yaml | 41 - logicpd,dm3730-som-lv-devkit # LogicPD Zoom OMAP35xx SOM-LV Development Kit
42 - logicpd,dm3730-torpedo-devkit # LogicPD Zoom OMAP35xx Torpedo Development Kit
83 - logicpd,dm3730-som-lv-devkit # LogicPD Zoom DM3730 SOM-LV Development Kit
84 … - logicpd,dm3730-torpedo-devkit # LogicPD Zoom DM3730 Torpedo + Wireless Development Kit
|
| /linux/sound/soc/sof/ |
| H A D | Kconfig | 78 Distributions should not select this option, only SOF development
80 Say Y if you are involved in SOF development and need this option.
93 Say Y if you are involved in SOF development and need this option.
126 If you are not involved in SOF releases and CI development,
137 Say Y if you are involved in SOF development and need this option.
|
| /linux/Documentation/networking/device_drivers/wifi/intel/ |
| H A D | ipw2200.rst | 89 part of a development project. Conformance to local regulatory
92 solution intended to be used for purposes other than development, please
177 of the ipw2200 development snapshot releases available from the
452 Due to the nature of open source development projects, there are
455 development snapshot releases.
459 major.minor.development
461 Any version where the 'development' portion is 0 (for example
465 Any version where the 'development' portion is not a 0 (for
466 example 1.0.1, 1.1.5, etc.) indicates a development version that is
468 and functionality of the development releases are not know. We make
|
| /linux/arch/mips/mobileye/ |
| H A D | Kconfig | 18 bool "Include FDT for Mobileye EyeQ5 development platforms"
22 Enable this to include the FDT for the EyeQ5 development platforms
|
| /linux/arch/arm/boot/dts/renesas/ |
| H A D | r8a7744-iwg20d-q7-dbcm-ca.dts | 3 * Device Tree Source for the iWave Systems RZ/G1N Qseven board development
15 model = "iWave Systems RZ/G1N Qseven development platform with camera add-on";
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-db-88f6281.dts | 3 * Marvell DB-88F6281-BP Development Board Setup
16 model = "Marvell DB-88F6281-BP Development Board";
|