Development: How to submit patches: Difference between revisions
Jump to navigation
Jump to search
m (fixed link) |
(change mailing list info!) |
||
| Line 1: | Line 1: | ||
=== Patch Preparation === |
=== Patch Preparation === |
||
Patches should be created against the |
Patches should be created against the V4L-DVB mercurial tree; see [[How to build from Mercurial]]. |
||
For references on how to develop a driver, take a look at [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel]. |
For references on how to develop a driver, take a look at [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel]. |
||
Post your patches to the [ |
Post your patches to the [mailto:majordomo@vger.kernel.org?body=subscribe%20linux-media linux-media] Mailing List for review and testing. |
||
Follow the guidelines in [http://lxr.linux.no/source/Documentation/SubmittingPatches Documentation/SubmittingPatches] (cf. [http://linux.yyz.us/patch-format.html jgarzik's version]), including: |
Follow the guidelines in [http://lxr.linux.no/source/Documentation/SubmittingPatches Documentation/SubmittingPatches] (cf. [http://linux.yyz.us/patch-format.html jgarzik's version]), including: |
||
| Line 18: | Line 18: | ||
Hint: [[Development: Linux Kernel patch submittal checklist|There's a checklist for patch submission ]] |
Hint: [[Development: Linux Kernel patch submittal checklist|There's a checklist for patch submission ]] |
||
Subscription to the [ |
Subscription to the [http://vger.kernel.org/vger-lists.html#linux-media linux-media mailing list] is recommended but not required. |
||
The patch will be applied to the main mercurial tree. Once tested and integrated, patches are merged into a git tree by the |
The patch will be applied to the main mercurial tree. Once tested and integrated, patches are merged into a git tree by the V4L-DVB maintainer and periodically pulled by Linus. |
||
Revision as of 23:53, 14 January 2009
Patch Preparation
Patches should be created against the V4L-DVB mercurial tree; see How to build from Mercurial.
For references on how to develop a driver, take a look at Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel.
Post your patches to the linux-media Mailing List for review and testing.
Follow the guidelines in Documentation/SubmittingPatches (cf. jgarzik's version), including:
- Verify best-practice kernel coding style
- Use [PATCH] in the subject line to get attention
- Explain what the patch does and what hardware it applies to
- Document your work where appropriate, in the form of patches to Documentation/video4linux files
- Add a Signed-off-by: Your name <name@yoursite.com> as a Developer's Certificate of Origin 1.1
- Fix any problems and repeat until everyone is happy ;)
- Send the patch inline, not as an attachment
Hint: There's a checklist for patch submission
Subscription to the linux-media mailing list is recommended but not required.
The patch will be applied to the main mercurial tree. Once tested and integrated, patches are merged into a git tree by the V4L-DVB maintainer and periodically pulled by Linus.