Changes

<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

git clone https://src.openvz.org/scm/ovz/vzkernel.git

As with the upstream kernel, modifications to the code should conform to the [https://www.kernel.org/doc/Documentation/CodingStyle Linux kernel coding style].

Use <code>git format-patch</code> 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 <code>devel (AT) openvz.org</code> mailing list, preferably using <code>git send-email</code>.

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 <code>devel-join (AT) openvz.org</code>

# 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.}}

* [[Contribute]]

* [[Kernel build]]

* [[Remote console setup]]

* https://www.kernel.org/doc/Documentation/CodingStyle

* http://book.git-scm.com/