[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55d76224-3019-6614-70ce-ba260bbcd54f@users.sourceforge.net>
Date: Wed, 18 Oct 2017 18:43:10 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
linux-integrity@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Cc: Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Julia Lawall <julia.lawall@...6.fr>,
Alexander Steffen <Alexander.Steffen@...ineon.com>,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Corentin Labbe <clabbe.montjoie@...il.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Jerry Snitselaar <jsnitsel@...hat.com>,
Kenneth Goldman <kgold@...ux.vnet.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
Nayna Jain <nayna@...ux.vnet.ibm.com>,
Paul Mackerras <paulus@...ba.org>,
Peter Hüwe <PeterHuewe@....de>,
Stefan Berger <stefanb@...ux.vnet.ibm.com>
Subject: Re: char/tpm: Improve a size determination in nine functions
> Commit message should just describe in plain text what you are doing
Did other contributors find the wording “Replace …”
> and why.
and “… a bit safer according to the Linux coding style convention.”
sufficient often enough already?
Which description would you find more appropriate for this change pattern?
Regards,
Markus
Powered by blists - more mailing lists