Difference between revisions of "Kernel patches"
(Marked this version for translation) |
(Tags: Mobile edit, Mobile web edit) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Virtuozzo}} | {{Virtuozzo}} | ||
| − | + | 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 | ||
| − | == Source code == | + | == Source code == |
| − | + | 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 | ||
| − | |||
| − | |||
| − | |||
| − | |||
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 == | + | == Editing == |
| − | |||
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 == | + | == Preparing patches == |
| − | |||
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 === | + | === Checkpatch === |
| − | |||
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 | ||
| − | + | ./scripts/checkpatch.pl *.patch | |
| − | ./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. | 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 == | + | == Sending patches == |
| − | |||
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>. | ||
| − | |||
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: | ||
| − | |||
# 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 | ||
| − | |||
{{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 == | + | == See also == |
* [[Contribute]] | * [[Contribute]] | ||
* [[Kernel build]] | * [[Kernel build]] | ||
| Line 64: | Line 48: | ||
* [[Remote console setup]] | * [[Remote console setup]] | ||
| − | == External links == | + | == 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 | ||
| − | |||
[[Category:Development]] | [[Category:Development]] | ||
Latest revision as of 18:39, 13 July 2021
This article is for Virtuozzo 7 only.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.
Contents
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:
- 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. |
See also[edit]
- Contribute
- Kernel build
- Kernel versioning
- Kernel flavors
- Kernel configuration
- Porting the kernel
- Hardware testing
- Remote console setup
