Difference between revisions of "Kernel patches"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(Marked this version for translation)
(rm translate tags)
Line 1: Line 1:
 
{{Virtuozzo}}
 
{{Virtuozzo}}
  
<translate>
 
<!--T:1-->
 
 
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.
 
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 == <!--T:2-->
+
== Source code ==
  
<!--T:3-->
+
Kernel source code is available from git repository at https://src.openvz.org/projects/OVZ/repos/vzkernel/browse
Kernel source code is available from git repository at
 
  
<!--T:4-->
 
https://src.openvz.org/projects/OVZ/repos/vzkernel/browse
 
 
<!--T:5-->
 
 
To clone, use
 
To clone, use
 
   
 
   
 
  git clone https://src.openvz.org/scm/ovz/vzkernel.git
 
  git clone https://src.openvz.org/scm/ovz/vzkernel.git
  
== Editing == <!--T:6-->
+
== Editing ==
  
<!--T:7-->
 
 
As with the upstream kernel, modifications to the code should conform to the [https://www.kernel.org/doc/Documentation/CodingStyle Linux kernel coding style].
 
As with the upstream kernel, modifications to the code should conform to the [https://www.kernel.org/doc/Documentation/CodingStyle Linux kernel coding style].
  
== Preparing patches == <!--T:8-->
+
== Preparing patches ==
  
<!--T:9-->
 
 
Use <code>git format-patch</code> to prepare your patches. See git documentation for more info.
 
Use <code>git format-patch</code> to prepare your patches. See git documentation for more info.
  
=== Checkpatch === <!--T:10-->
+
=== Checkpatch ===
  
<!--T:11-->
 
 
There is a tool (scripts/checkpatch.pl) that '''should''' be used to check your patches. Use
 
There is a tool (scripts/checkpatch.pl) that '''should''' be used to check your patches. Use
  
  <!--T:12-->
+
  ./scripts/checkpatch.pl *.patch
./scripts/checkpatch.pl *.patch
 
  
<!--T:13-->
 
 
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.
 
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 == <!--T:14-->
+
== Sending patches ==
  
<!--T:15-->
 
 
Please send your patches to <code>devel (AT) openvz.org</code> mailing list, preferably using <code>git send-email</code>.
 
Please send your patches to <code>devel (AT) openvz.org</code> mailing list, preferably using <code>git send-email</code>.
  
<!--T:16-->
 
 
You need to be subscribed in order to post. The list is managed by mailman, there are two ways to subscribe:
 
You need to be subscribed in order to post. The list is managed by mailman, there are two ways to subscribe:
  
<!--T:17-->
 
 
# Send an email to <code>devel-join (AT) openvz.org</code>
 
# Send an email to <code>devel-join (AT) openvz.org</code>
 
# Use a web interface at https://lists.openvz.org/mailman/listinfo/devel
 
# Use a web interface at https://lists.openvz.org/mailman/listinfo/devel
  
<!--T:18-->
 
 
{{Note|You need to be subscribed first in order to be able to post.}}
 
{{Note|You need to be subscribed first in order to be able to post.}}
  
== See also == <!--T:19-->
+
== See also ==
 
* [[Contribute]]
 
* [[Contribute]]
 
* [[Kernel build]]
 
* [[Kernel build]]
Line 64: Line 48:
 
* [[Remote console setup]]
 
* [[Remote console setup]]
  
== External links == <!--T:20-->
+
== External links ==
 
* https://www.kernel.org/doc/Documentation/CodingStyle
 
* https://www.kernel.org/doc/Documentation/CodingStyle
 
* 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]]

Revision as of 02:51, 27 November 2018

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

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

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

Preparing patches

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

Checkpatch

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

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

External links