Development: How to submit patches: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
:* Fix any problems and repeat until everyone is happy ;) |
:* Fix any problems and repeat until everyone is happy ;) |
||
:* Send the patch inline, not as an attachment |
:* Send the patch inline, not as an attachment |
||
Hint: [[ CheckList | There's a checklist for patch submission ]] |
|||
Subscription to the [https://www.redhat.com/mailman/listinfo/video4linux-list V4l mailing list] is recommended but not required. |
Subscription to the [https://www.redhat.com/mailman/listinfo/video4linux-list V4l mailing list] is recommended but not required. |
||
Revision as of 13:39, 7 February 2007
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 video4linux 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 V4l 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 maintainer and periodically pulled by Linus.