-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCONTRIBUTING.TXT
50 lines (33 loc) · 1.36 KB
/
CONTRIBUTING.TXT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Contributors Guide
==================
This document outlines how to contribute code to the DTS project.
Getting the code
----------------
The DTS code can be cloned from the repository on dpdk.org as follows:
git clone git://dpdk.org/tools/dts
git clone http://dpdk.org/git/tools/dts
The code can be browsed at http://dpdk.org/browse/tools/dts/
Submitting Patches
------------------
Contributions to DTS should be submitted as git formatted patches to the
DTS mailing list: dts@dpdk.org
Note you must first register for the mailing list at:
http://dpdk.org/ml/listinfo/dts
The commit message must end with a "Signed-off-by:" line which is added using:
git commit --signoff # or -s
The purpose of the signoff is explained in the Linux kernel guidelines
Developer's Certificate of Origin:
http://www.kernel.org/doc/Documentation/SubmittingPatches
Note:
All developers must ensure that they have read, understood and complied
with the Developer's Certificate of Origin section of the documentation
prior to applying the signoff and submitting a patch.
The DPDK Code Contributors guidelines contain information that is
useful for submitting patches to DTS:
http://dpdk.org/doc/guides/contributing/index.html
Coding Guidelines
-----------------
* Python code should follow PEP8.
Maintainer
----------
The DTS maintainer is: Marvin Liu <yong.liu@intel.com>