Kernel patches - Revision history

99.227.74.184 at 18:39, 13 July 2021

2021-07-13T18:39:12Z

Kir: rm translate tags

2018-11-27T02:51:07Z

rm translate tags

Sergey Bronnikov: Marked this version for translation

2015-12-29T08:32:10Z

Marked this version for translation

Sergey Bronnikov: mark article for translation

2015-12-29T08:31:53Z

mark article for translation

Sergey Bronnikov: Mark as article for Virtuozzo

2015-06-06T18:33:24Z

Mark as article for Virtuozzo

Sergey Bronnikov: Virtuozzo category

2015-06-06T18:20:54Z

Virtuozzo category

Sergey Bronnikov at 13:54, 2 June 2015

2015-06-02T13:54:42Z

Kir: links, categories

2015-04-28T18:11:16Z

links, categories

Kir: created (draft)

2015-04-28T18:06:40Z

created (draft)

New page

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 [https://www.kernel.org/doc/Documentation/CodingStyle Linux kernel coding style].

== Preparing patches ==

Use <code>git format-patch</code> 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 <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.}}

@@ Line 1: / Line 1: @@
 {{Virtuozzo}}
-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 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 ==

@@ Line 1: / Line 1: @@
 {{Virtuozzo}}
 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
 To clone, use
   git clone https://src.openvz.org/scm/ovz/vzkernel.git
-== Editing == <!--T:6-->
+== 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].
-== Preparing patches == <!--T:8-->
+== Preparing patches ==
 Use <code>git format-patch</code> to prepare your patches. See git documentation for more info.
-=== Checkpatch === <!--T:10-->
+=== Checkpatch ===
 There is a tool (scripts/checkpatch.pl) that '''should''' be used to check your patches. Use
-  <!--T:12-->
+  ./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 == <!--T:14-->
+== Sending patches ==
 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.}}
-== See also == <!--T:19-->
+== See also ==
 * [[Contribute]]
 * [[Kernel build]]
@@ Line 64: / Line 48: @@
 * [[Remote console setup]]
-== External links == <!--T:20-->
+== External links ==
 * https://www.kernel.org/doc/Documentation/CodingStyle
 * http://book.git-scm.com/
 * http://git-scm.com/documentation
 [[Category:Development]]

@@ Line 1: / Line 1: @@
 {{Virtuozzo}}
 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.
@@ Line 54: / Line 55: @@
 * http://book.git-scm.com/
 * http://git-scm.com/documentation
 [[Category:Development]]

← Older revision		Revision as of 18:33, 6 June 2015
Line 1:		Line 1:
		+	{{Virtuozzo}}
		+
	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.

@@ Line 55: / Line 55: @@
 [[Category:Development]]
 [[Category:Kernel]]
-[[Category: Contributions]]
+[[Category:Contributions]]

← Older revision		Revision as of 13:54, 2 June 2015
Line 55:		Line 55:
	[[Category:Development]]		[[Category:Development]]
	[[Category:Kernel]]		[[Category:Kernel]]
		+	[[Category: Contributions]]

← Older revision		Revision as of 18:11, 28 April 2015
Line 37:		Line 37:

	{{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 ==
		+	* [[Contribute]]
		+	* [[Kernel build]]
		+	* [[Kernel versioning]]
		+	* [[Kernel flavors]]
		+	* [[Kernel configuration]]
		+	* [[Porting the kernel]]
		+	* [[Hardware testing]]
		+	* [[Remote console setup]]
		+
		+	== External links ==
		+	* https://www.kernel.org/doc/Documentation/CodingStyle
		+	* http://book.git-scm.com/
		+	* http://git-scm.com/documentation
		+
		+	[[Category:Development]]
		+	[[Category:Kernel]]