|
Size: 419
Comment: beginnings of "how to merge code upstream"
|
Size: 626
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| * ["/MergingStrategy"] strategies for merging code upstream. * ["/WhatNotToDo"] what you should never do if you want to merge upstream. |
|
| Line 5: | Line 7: |
| * ["/SubmittingDrivers"] how to submit device drivers to the linux kernel (from the kernel tree) * ["/SubmittingPatches"] how to submit patches to the linux kernel (from the kernel tree) |
Helpful documents from the kernel tree: * ["/SubmittingDrivers"] how to submit device drivers to the linux kernel. * ["/SubmittingPatches"] how to submit patches to the linux kernel. * ["/SubmitChecklist"] a checklist for submitting code upstream. |
This section of the Kernelnewbies site is meant as a guide on how to get code merged into the upstream kernel.
["/WhyMergeUpstream"] why should I merge my code into the upstream kernel?
["/MergingStrategy"] strategies for merging code upstream.
["/WhatNotToDo"] what you should never do if you want to merge upstream.
Helpful documents from the kernel tree:
["/SubmittingDrivers"] how to submit device drivers to the linux kernel.
["/SubmittingPatches"] how to submit patches to the linux kernel.
["/SubmitChecklist"] a checklist for submitting code upstream.