Lines Matching refs:of
7 contain anything related to the technical aspects of kernel programming,
10 If anything in this document becomes out of date, please send in patches
11 to the maintainer of this file, who is listed at the bottom of the
23 explain some of the reasons why the community works like it does.
26 parts written in assembly. A good understanding of C is required for
29 are not a good substitute for a solid C education and/or years of
36 adheres to the ISO C89 standard, it uses a number of extensions that are
39 portions of the C standard are not supported. Arbitrary long long
47 existing development community. It is a diverse group of people, with
51 possible about these standards ahead of time, as they are well
53 of doing things.
60 file, COPYING, in the main directory of the source tree, for details on
73 The Linux kernel source tree has a large range of documents that are
83 Here is a list of files that are in the kernel source tree that are
91 This file gives a list of the minimum levels of various software
96 This describes the Linux kernel coding style, and some of the
113 Other excellent descriptions of how to create patches properly are:
139 it), as it resolves a lot of common misconceptions and confusion
140 about the unique behavior of kernel maintainers.
144 happen, and what to do if you want to get a change into one of these
148 A list of external documentation that pertains to kernel
154 apply it to the different development branches of the kernel.
156 The kernel also has a large number of documents that can be
158 full description of the in-kernel API, and rules on how to handle
175 It consists of a helpful mailing list where you can ask almost any type
176 of basic kernel development question (make sure to search the archives
179 real-time, and a lot of helpful documentation that is useful for
183 and current projects (both in-tree and out-of-tree). It also describes
191 It is a great place to start. It describes a list of relatively simple
193 source tree. Working with the developers in charge of this project, you
194 will learn the basics of getting your patch into the Linux kernel tree,
195 and possibly be pointed in the direction of what to go work on next, if
198 If you already have a chunk of code that you want to put into the kernel
207 bits are commented well), perhaps even with the help of specialized
211 repository of the kernel code may be found at:
218 Linux kernel development process currently consists of a few different
219 main kernel "branches" and lots of different subsystem-specific kernel
233 during this period of time maintainers can submit big diffs to
241 stability of the whole kernel. Please note that a whole new driver
243 risk of causing regressions with such a change as long as the change
244 is self-contained and does not affect areas outside of the code that
254 linux-kernel mailing list. The goal is to reduce the length of
256 the real world, a small number of regressions often remain at
285 documents what kinds of changes are acceptable for the -stable tree, and
290 These are daily snapshots of Linus' kernel tree which are managed in a
292 daily and represent the current state of Linus' tree. They are more
298 The maintainers of the various kernel subsystems --- and also many
299 kernel subsystem developers --- expose their current state of
301 happening in the different areas of the kernel. In areas where
306 Most of these repositories are git trees, but there are also other SCMs
307 in use, or patch queues being published as quilt series. Addresses of
309 of them can be browsed at http://git.kernel.org/.
317 accepted, or rejected. Most of these patchwork sites are listed at
343 of information is needed by the kernel developers to help track down the
350 One of the best ways to put into practice your hacking skills is by fixing
353 your skills, and other developers will be aware of your presence. Fixing
354 bugs is one of the best ways to get merits among other developers, because
358 If you want to be advised of the future bug reports, you can subscribe to the
370 As some of the above documents describe, the majority of the core kernel
374 There are archives of the mailing list on the web in many different
378 you want to bring up, before you post it to the list. A lot of things
382 Most of the individual kernel subsystems also have their own separate
384 MAINTAINERS file for a list of what these lists are for the different
387 Many of the lists are hosted on kernel.org. Information on them can be
396 If multiple people respond to your mail, the CC: list of recipients may
402 Remember to keep the context and the attribution of your replies intact,
403 keep the "John Kernelhacker wrote ...:" lines at the top of your reply, and
404 add your statements between the individual quoted sections instead of
405 writing at the top of the mail.
410 to comment on individual lines of your patch, which works only that way.
422 The goal of the kernel community is to provide the best possible kernel
432 Remember, this is part of getting your patch into the kernel. You have
443 - resubmit the patch without making any of the requested changes
453 of a dozen things you should correct. This does _not_ imply that your
463 development environments. Here are a list of things that you can try to
467 - "This deletes 2000 lines of code."
470 - "Here is a series of small patches that..."
482 - "I rewrote all of the current mess, and here it is..."
486 software engineering work environments is the faceless nature of
487 interaction. One benefit of using email and irc as the primary forms of
488 communication is the lack of discrimination based on gender or race.
489 The Linux kernel work environment is accepting of women and minorities
497 comfortable with English. A good grasp of the language can be needed in
506 The Linux kernel community does not gladly accept large chunks of code
509 the exact opposite of what companies are used to doing. Your proposal
515 that almost all of the time.
524 proportional to the size of the patch, or something).
535 "Think of a teacher grading homework from a math student. The
542 The same is true of kernel development. The maintainers and
579 ChangeLog section of the document:
586 All of these things are sometimes very hard to do. It can take years to
587 perfect these practices (if at all). It's a continuous process of
588 improvement that requires a lot of patience and determination. But
599 Huizenga for some of the list of things you should and should not say.