Lines Matching full:are
31 are not a good substitute for a solid C education and/or years of
32 experience, the following books are good for, if anything, reference:
39 adheres to the ISO C11 standard, it uses a number of extensions that are
42 portions of the C standard are not supported. Arbitrary long long
43 divisions and floating point are not allowed. It can sometimes be
49 Please remember that you are trying to learn how to work with the
54 possible about these standards ahead of time, as they are well
64 rules and how to use `SPDX <https://spdx.org/>`_ identifiers in source code are
67 not ask on the Linux kernel mailing list. The people on the mailing lists are
78 The Linux kernel source tree has a large range of documents that are
80 new features are added to the kernel, it is recommended that new
81 documentation files are also added which explain how to use the feature.
87 Here is a list of files that are in the kernel source tree that are
93 who are new to the kernel should start here.
97 packages that are necessary to build and run the kernel
104 patches if these rules are followed, and many people will only
115 Following these rules will not guarantee success (as all patches are
119 Other excellent descriptions of how to create patches properly are:
160 are looking for within the in-kernel documentation.
221 bits are commented well), perhaps even with the help of specialized
235 branches. These different branches are:
253 can be found at https://git-scm.com/) but plain patches are also just
257 should fix a regression. Bugs that have always existed are not
258 regressions, so only push these kinds of fixes if they are important.
281 Kernels with 3-part versions are -stable kernels. They contain
288 kernel and are not interested in helping test development/experimental
291 Stable trees are maintained by the "stable" team <stable@vger.kernel.org>, and
292 are released as needs dictate. The normal release period is approximately
293 two weeks, but it can be longer if there are no pressing problems. A
298 in the kernel tree documents what kinds of changes are acceptable for
310 submission and other already ongoing work are avoided.
312 Most of these repositories are git trees, but there are also other SCMs
314 these subsystem repositories are listed in the MAINTAINERS file. Many
323 accepted, or rejected. Most of these patchwork sites are listed at
329 Before updates from subsystem trees are merged into the mainline tree,
331 testing repository exists into which virtually all subsystem trees are
338 Adventurous testers are very welcome to runtime-test the linux-next.
360 To work on already reported bug reports, find a subsystem you are interested in.
378 There are archives of the mailing list on the web in many different
385 already discussed in detail are only recorded at the mailing list
390 MAINTAINERS file for a list of what these lists are for the different
393 Many of the lists are hosted on kernel.org. Information on them can be
415 If you add patches to your mail, make sure they are plain readable text
446 If there are no responses to your posting, wait a few days and try
460 Remember, being wrong is acceptable as long as you are willing to work
474 development environments. Here are a list of things that you can try to
504 because all you are is an email address. The international aspect also
510 The language barrier can cause problems for some people who are not
523 the exact opposite of what companies are used to doing. Your proposal
525 you can receive feedback on what you are doing. It also lets the
526 community feel that you are working with them, and not simply using them
531 The reasons for breaking things up are the following:
570 that are unfinished and will be "fixed up later."
601 All of these things are sometimes very hard to do. It can take years to
605 start exactly where you are now.