Optimization so that the reviewer can weigh costs against benefits. Memory, and readability or, when it comes to heuristics, betweenĭifferent workloads. Optimizations usually aren't free but trade-offs between CPU, Performance, memory consumption, stack footprint, or binary size, Vendor/product-specific trees that cherry-pick only specific patchesįrom upstream, so include anything that could help route your changeĭownstream: provoking circumstances, excerpts from dmesg, crashĭescriptions, performance regressions, latency spikes, lockups, etc. Installations run kernels from secondary stable trees or Problem was spotted during code review, describe the impact you think Pretty convincing, but not all bugs are that blatant. Problem worth fixing and that it makes sense for them to read past theĭescribe user-visible impact. Whether your patch is a one-line bug fix orĥ000 lines of a new feature, there must be an underlying problem that _describe_changes: Describe your changes -ĭescribe your problem. In the MAINTAINERS file to find that tree, or simply ask the maintainer if Most subsystem maintainers run their own trees and want to see Note, however, that you may not want to develop against the mainline treeĭirectly. Which can be grabbed with :: git clone git:///pub/scm/linux/kernel/git/torvalds/linux.git You'll want to start with the mainline repository, If you do not have a repository with the current kernel source handy, use :ref: `Documentation/process/maintainer-handbooks.rst `. Some subsystems and maintainer trees have additional information about Use it, it will make your life as a kernel developer and in general much If you're unfamiliar with ``git``, you would be well-advised to learn how to This documentation assumes that you're using ``git`` to prepare your patches. If you are submittingĪ driver, also read Documentation/process/submitting-drivers.rst for deviceĭocumentation/devicetree/bindings/submitting-patches.rst. Also, readĭocumentation/process/submit-checklist.rstįor a list of items to check before submitting code.
Works, see Documentation/process/development-process.rst. For detailed information on how the kernel development process This document contains a large number of suggestions in a relatively terseįormat. With "the system." This text is a collection of suggestions whichĬan greatly increase the chances of your change being accepted.
Kernel, the process can sometimes be daunting if you're not familiar _submittingpatches: Submitting patches: the essential guide to getting your code into the kernel =įor a person or company who wishes to submit a change to the Linux
0 kommentar(er)
