From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id A53D51B1A7 for ; Tue, 9 Jan 2018 16:51:37 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jan 2018 07:51:36 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,336,1511856000"; d="scan'208";a="8719111" Received: from silpixa00399502.ir.intel.com (HELO silpixa00399502.ger.corp.intel.com) ([10.237.223.218]) by fmsmga002.fm.intel.com with ESMTP; 09 Jan 2018 07:51:35 -0800 From: Marko Kovacevic To: dev@dpdk.org Cc: john.mcnamara@intel.com, Marko Kovacevic Date: Tue, 9 Jan 2018 15:51:00 +0000 Message-Id: <20180109155101.12165-1-marko.kovacevic@intel.com> X-Mailer: git-send-email 2.9.5 Subject: [dpdk-dev] [PATCH v1 1/2] doc: add guidelines for coverity tags X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 15:51:38 -0000 Added contribution guideline for adding tags when sending patches that have been raised by coverity Signed-off-by: Marko Kovacevic --- doc/guides/contributing/patches.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index 64408e7..e6b6e80 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -257,6 +257,26 @@ 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 `_ is a gratis +static-analysis cloud-based service for the open source community. It is a tool for +C,C++,C# and Java it is used for finding bugs through static analysis. If a patch +fix is being sent to the mailing list due to a Coverity related issue,a +Coverity issue tag should be inserted into the commit message body as so:: + + 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 + + Creating Patches ---------------- -- 2.9.5