doc: add contribution guidelines for coverity tags
authorMarko Kovacevic <marko.kovacevic@intel.com>
Tue, 16 Jan 2018 09:12:46 +0000 (09:12 +0000)
committerThomas Monjalon <thomas@monjalon.net>
Thu, 24 May 2018 16:48:54 +0000 (18:48 +0200)
Added contribution guideline for adding tags
when sending patches that have been raised by
coverity

Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
doc/guides/contributing/patches.rst

index 2287835..24fd671 100644 (file)
@@ -256,6 +256,27 @@ In addition to the ``Signed-off-by:`` name the commit messages can also have
 tags for who reported, suggested, tested and reviewed the patch being
 posted. Please refer to the `Tested, Acked and Reviewed by`_ section.
 
+Coverity Related Patch Fixes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+`Coverity <https://scan.coverity.com/projects/dpdk-data-plane-development-kit>`_
+is a tool for static code analysis.
+It is used as a cloud-based service used to scan the DPDK source code,
+and alert developers of any potential defects in the source code.
+When fixing an issue found by Coverity, the patch must contain a Coverity issue ID
+in the body of the commit message. For example::
+
+
+     doc: fix some parameter description
+
+     Update the docs, fixing description of some parameter.
+
+     Coverity issue: 12345
+     Fixes: abcdefgh1234 ("doc: add some parameter")
+     Cc: author@example.com
+
+     Signed-off-by: Alex Smith <alex.smith@example.com>
+
 
 Creating Patches
 ----------------