From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751899AbdJRO5q (ORCPT ); Wed, 18 Oct 2017 10:57:46 -0400 Received: from mga02.intel.com ([134.134.136.20]:53869 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751276AbdJRO5o (ORCPT ); Wed, 18 Oct 2017 10:57:44 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,397,1503385200"; d="scan'208";a="911145236" Date: Wed, 18 Oct 2017 17:57:35 +0300 From: Jarkko Sakkinen To: SF Markus Elfring Cc: Mimi Zohar , linux-integrity@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Julia Lawall , Alexander Steffen , linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, Andy Shevchenko , Benjamin Herrenschmidt , Corentin Labbe , Jason Gunthorpe , Jerry Snitselaar , Kenneth Goldman , Michael Ellerman , Nayna Jain , Paul Mackerras , Peter =?iso-8859-1?Q?H=FCwe?= , Stefan Berger Subject: Re: char/tpm: Improve a size determination in nine functions Message-ID: <20171018145735.lpzwakatsty7emlw@linux.intel.com> References: <1d3516a2-a8e6-9e95-d438-f115fac84c7f@users.sourceforge.net> <83a166af-aecc-649d-dfe3-a72245345209@users.sourceforge.net> <1508238182.16112.475.camel@linux.intel.com> <1508244757.4234.60.camel@linux.vnet.ibm.com> <1508253453.4234.81.camel@linux.vnet.ibm.com> <9689f036-ba9f-d23b-cf89-c289bc308771@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9689f036-ba9f-d23b-cf89-c289bc308771@users.sourceforge.net> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 17, 2017 at 08:41:04PM +0200, SF Markus Elfring wrote: > Do you find my wording “This issue was detected by using the > Coccinelle software.” insufficient? This is fine for cover letter, not for the commits. After your analysis software finds an issue you should manually analyze what is wrong and document that to the commit message. This applies to sparse, coccinelle or any other tool. Tool-based commit messages are bad for commit history where as clean description gives idea what was done (if you have to maintain a GIT tree). In my opinion tool is doing all the work but the part that you should do is absent. > Regards, > Markus /Jarkko