[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f441fd9a5452bf2943e5dbe6d74b5d5f26016a90.camel@linux.intel.com>
Date: Fri, 09 Aug 2019 23:28:13 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Stephen Boyd <swboyd@...omium.org>, Peter Huewe <peterhuewe@....de>
Cc: linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org,
Andrey Pronin <apronin@...omium.org>,
Duncan Laurie <dlaurie@...omium.org>,
Jason Gunthorpe <jgg@...pe.ca>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Guenter Roeck <groeck@...omium.org>,
Alexander Steffen <Alexander.Steffen@...ineon.com>
Subject: Re: [PATCH v3 2/4] tpm: tpm_tis_spi: Export functionality to other
drivers
On Tue, 2019-08-06 at 15:07 -0700, Stephen Boyd wrote:
> We want to use most of the code in this driver, except we want to modify
> the flow control and idle behavior. Let's "libify" this driver so that
> another driver can call the code in here and slightly tweak the
> behavior.
Neither "libifying" nor "slightly tweaking" gives an idea what the
commit does. A great commit message should be in imperative form
describe what it does and why in as plain english as possible.
Often commit messages are seen just as a necessary bad and not much
energy is spent on them but for a maitainer solid commit messages have
an indispensable value.
> + void (*pre_transfer)(struct tpm_tis_spi_phy *phy);
Adding a new calback should be a commit of its own.
/Jarkko
Powered by blists - more mailing lists