Difference between revisions of "Kernel patches"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(mark article for translation)
(Tags: Mobile edit, Mobile web edit)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Virtuozzo}}
 
{{Virtuozzo}}
  
<translate>
+
This document describes how to contribute your patches to the OpenVZ k#ernel. 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.
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.
 
  
 
== Source code ==
 
== Source code ==
  
Kernel source code is available from git repository at
+
Kernel source code is available from git repository at https://src.openvz.org/projects/OVZ/repos/vzkernel/browse
 
 
https://src.openvz.org/projects/OVZ/repos/vzkernel/browse
 
  
 
To clone, use
 
To clone, use
Line 55: Line 52:
 
* http://book.git-scm.com/
 
* http://book.git-scm.com/
 
* http://git-scm.com/documentation
 
* http://git-scm.com/documentation
</translate>
 
  
 
[[Category:Development]]
 
[[Category:Development]]

Latest revision as of 18:39, 13 July 2021

This document describes how to contribute your patches to the OpenVZ k#ernel. 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.

Source code[edit]

Kernel source code is available from git repository at https://src.openvz.org/projects/OVZ/repos/vzkernel/browse

To clone, use

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

Editing[edit]

As with the upstream kernel, modifications to the code should conform to the Linux kernel coding style.

Preparing patches[edit]

Use git format-patch to prepare your patches. See git documentation for more info.

Checkpatch[edit]

There is a tool (scripts/checkpatch.pl) that should be used to check your patches. Use

./scripts/checkpatch.pl *.patch

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.

Sending patches[edit]

Please send your patches to devel (AT) openvz.org mailing list, preferably using git send-email.

You need to be subscribed in order to post. The list is managed by mailman, there are two ways to subscribe:

  1. Send an email to devel-join (AT) openvz.org
  2. Use a web interface at https://lists.openvz.org/mailman/listinfo/devel
Yellowpin.svg Note: You need to be subscribed first in order to be able to post.

See also[edit]

External links[edit]