Lines Matching refs:kernel

4 process, the proof of any kernel development project is in the resulting
10 number of ways in which kernel developers can go wrong.  Then the focus
19 The kernel has long had a standard coding style, described in
22 a substantial amount of code in the kernel which does not meet the coding
24 hazards for kernel developers.
26 The first of these is to believe that the kernel coding standards do not
28 code to the kernel is very difficult if that code is not coded according to
30 before they will even review it.  A code base as large as the kernel
35 Occasionally, the kernel's coding style will run into conflict with an
36 employer's mandated style.  In such cases, the kernel's style will have to
37 win before the code can be merged.  Putting code into the kernel means
41 The other trap is to assume that code which is already in the kernel is
44 as a way of getting their name into the kernel changelogs - or both.  But
61 Certainly the kernel makes extensive use of abstraction; no project
81 penalty; they do not belong in the Linux kernel.
84 from another kernel subsystem, it is time to ask whether it would, in fact,
87 replicating the same code throughout the kernel.
100 is used within the kernel.  But there is little desire to see code which is
122 at each call site, they end up bloating the size of the compiled kernel.
129 In general, kernel programmers ignore cache effects at their peril.  The
144 mainline kernel.  This donation was welcome news; support for wireless
156 Once upon a time, Linux kernel code could be developed without thinking
160 raise the level of concurrency within the kernel.  The days when kernel
177 regressions have become most unwelcome in the mainline kernel.  With few
210 kernel.  To that end, the kernel developers have put together an impressive
225 kernel with "make EXTRA_CFLAGS=-W" to get the full set.
227 The kernel provides several configuration options which turn on debugging
228 features; most of these are found in the "kernel hacking" submenu.  Several
229 of these options should be turned on for any kernel used for development or
236    warnings from other parts of the kernel.
239    created by the kernel and warn when things are done out of order.  If
268 As a diligent kernel programmer, you will, beyond doubt, check the return
275 The kernel provides a fault injection framework which can do exactly that,
286 user-space and kernel-space addresses, mixture of big-endian and
289 be found at https://sparse.wiki.kernel.org/index.php/Main_Page if your
295 problems.  Quite a few "semantic patches" for the kernel have been packaged
305 	http://www.kernel.org/pub/tools/crosstool/
313 Documentation has often been more the exception than the rule with kernel
315 of new code into the kernel, make life easier for other developers, and
333 The file Documentation/kernel-parameters.txt describes all of the kernel's
342 in a number of ways by the "kernel-doc" script.  If you are working within
347 beginning kernel developers.  The format of these comments, along with some
349 Documentation/kernel-doc-nano-HOWTO.txt.
351 Anybody who reads through a significant amount of existing kernel code will
369 The binary interface provided by the kernel to user space cannot be broken
370 except under the most severe circumstances.  The kernel's internal
372 the need arises.  If you find yourself having to work around a kernel API,
374 needs, that may be a sign that the API needs to change.  As a kernel
384 generally charged with the task of fixing any code within the kernel tree
397 something that kernel developers need to be worried about, but we also do