<translate> This document describes how to contribute your patches to the OpenVZ kernel. In a nutshell, the process is similar to the one for the upstream kernel — we use git for source control and a mailing list for communication.
Kernel source code is available from git repository at
To clone, use
As with the upstream kernel, modifications to the code should conform to the Linux kernel coding style.
git format-patch to prepare your patches. See git documentation for more info.
There is a tool (scripts/checkpatch.pl) that should be used to check your patches. Use
It will produce a detailed report on style problems in your patch(es). Make sure to fix all the errors (some warnings may be ignored) before sending.
Please send your patches to
devel (AT) openvz.org mailing list, preferably using
You need to be subscribed in order to post. The list is managed by mailman, there are two ways to subscribe:
- Send an email to
devel-join (AT) openvz.org
- Use a web interface at https://lists.openvz.org/mailman/listinfo/devel
|Note: You need to be subscribed first in order to be able to post.|
- Kernel build
- Kernel versioning
- Kernel flavors
- Kernel configuration
- Porting the kernel
- Hardware testing
- Remote console setup