Searched full:development (Results 1 – 25 of 211) sorted by relevance
123456789
| /Documentation/process/ |
| 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 …]
|
| D | development-process.rst | 3 A guide to the Kernel Development Process
22 work with the development community with a minimum of frustration. It is
25 development (or, indeed, free software development in general). While
|
| 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 thus 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 4.16 development cycle went (all dates in
[all …]
|
| D | 8.Conclusion.rst | 6 There are numerous sources of information on Linux kernel development and
18 Various web sites discuss kernel development at all levels of detail. Your
32 There are a number of books on kernel development:
38 Linux Kernel Development (Robert Love).
73 the direction of kernel development, and more. It is a situation where
|
| 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.
172 provide can help the development community provide useful input on the
200 of a kernel development project, the better off everybody involved will be.
207 need to keep development plans behind closed doors.
[all …]
|
| 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
137 This document is crucial for understanding the Linux development
139 development on other Operating Systems.
149 for anyone new to kernel development (or anyone simply curious about
160 development. Please consult this list if you do not find what you
165 apply it to the different development branches of the kernel.
[all …]
|
| D | embargoed-hardware-issues.rst | 87 community compliant development under embargo restrictions.
112 Due to the globally distributed nature of Linux kernel development,
139 development process.
154 participate in the mitigation development.
171 Mitigation development
177 Using a mailing-list is close to the normal Linux development process and
181 The mailing-list operates in the same way as normal Linux development.
185 development branch against the mainline kernel and backport branches for
190 time of the development process and needs to be handled in a timely manner.
205 by the incident team and brought into the development process.
[all …]
|
| 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
|
| D | index.rst | 8 Working with the kernel development community
26 development-process
|
| 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.
98 kernel development community; he can often unjam a situation which seems to
123 contents visible to the development community as a whole. At this point,
179 development community remembers developers who lose interest in their code
|
| /Documentation/ |
| D | conf.py | 64 copyright = 'The kernel development community'
65 author = 'The kernel development community'
387 'The kernel development community', 'manual'),
389 'The kernel development community', 'manual'),
391 'The kernel development community', 'manual'),
392 ('dev-tools/index', 'dev-tools.tex', 'Development tools for the Kernel',
393 'The kernel development community', 'manual'),
395 'The kernel development community', 'manual'),
397 'The kernel development community', 'manual'),
399 'The kernel development community', 'manual'),
[all …]
|
| /Documentation/maintainer/ |
| 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 …]
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | omap.txt | 121 - OMAP4 SDP : Software Development Board
136 - OMAP3 EVM : Software Development Board for OMAP35x, AM/DM37x
139 - AM335X EVM : Software Development Board for AM335x
160 - AM335X phyCORE-AM335x: Development kit
202 - DRA762 EVM: Software Development Board for DRA762
205 - DRA742 EVM: Software Development Board for DRA742
208 - DRA722 EVM: Software Development Board for DRA722
211 - DRA718 EVM: Software Development Board for DRA718
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | cirrus,lochnagar.txt | 1 Cirrus Logic Lochnagar Audio Development Board
3 Lochnagar is an evaluation and development board for Cirrus Logic
|
| /Documentation/dev-tools/ |
| D | index.rst | 2 Development tools for the kernel
5 This document is a collection of documents about development tools that can
|
| /Documentation/devicetree/bindings/arm/ |
| D | picoxcell.txt | 6 - "picochip,pc7302-pc3x3" : PC7302 development board with PC3X3 device.
7 - "picochip,pc7302-pc3x2" : PC7302 development board with PC3X2 device.
|
| /Documentation/devicetree/bindings/sound/ |
| D | cirrus,lochnagar.txt | 1 Cirrus Logic Lochnagar Audio Development Board
3 Lochnagar is an evaluation and development board for Cirrus Logic
|
| /Documentation/usb/ |
| 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.
|
| /Documentation/devicetree/bindings/nds32/ |
| D | andestech-boards | 27 efficiently. The optional hardware development platform further provides real
28 system environment for early prototyping and software/hardware co-development.
|
| /Documentation/filesystems/ |
| D | ecryptfs.txt | 13 This software is currently undergoing development. Make sure to
72 development, since secret values will be written out to the system log
|
| /Documentation/security/ |
| D | index.rst | 12 lsm-development
|
| /Documentation/networking/device_drivers/intel/ |
| D | ipw2200.txt | 82 part of a development project. Conformance to local regulatory
85 solution intended to be used for purposes other than development, please
169 of the ipw2200 development snapshot releases available from the
400 Due to the nature of open source development projects, there are
403 development snapshot releases.
407 major.minor.development
409 Any version where the 'development' portion is 0 (for example
413 Any version where the 'development' portion is not a 0 (for
414 example 1.0.1, 1.1.5, etc.) indicates a development version that is
416 and functionality of the development releases are not know. We make
|
| /Documentation/devicetree/bindings/mfd/ |
| D | cirrus,lochnagar.txt | 1 Cirrus Logic Lochnagar Audio Development Board
3 Lochnagar is an evaluation and development board for Cirrus Logic
|
| /Documentation/devicetree/bindings/regulator/ |
| D | cirrus,lochnagar.txt | 1 Cirrus Logic Lochnagar Audio Development Board
3 Lochnagar is an evaluation and development board for Cirrus Logic
|
| /Documentation/devicetree/bindings/arc/ |
| D | hsdk.txt | 1 Synopsys DesignWare ARC HS Development Kit Device Tree Bindings
|
123456789