From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, peterhuewe@gmx.de, jgg@ziepe.ca,
arnd@arndb.de
Subject: Re: [PATCH V3] tpm_tis_spi: use new 'delay' structure for SPI transfer delays
Date: Tue, 17 Dec 2019 14:04:29 +0200 [thread overview]
Message-ID: <9991700815c02b3227a5902e4cae1afe5200b0ff.camel@linux.intel.com> (raw)
In-Reply-To: <20191217091615.12764-1-alexandru.ardelean@analog.com>
On Tue, 2019-12-17 at 11:16 +0200, Alexandru Ardelean wrote:
> In a recent change to the SPI subsystem [1], a new 'delay' struct was added
> to replace the 'delay_usecs'. This change replaces the current
> 'delay_usecs' with 'delay' for this driver.
>
> The 'spi_transfer_delay_exec()' function [in the SPI framework] makes sure
> that both 'delay_usecs' & 'delay' are used (in this order to preserve
> backwards compatibility).
>
> [1] commit bebcfd272df6485 ("spi: introduce `delay` field for
> `spi_transfer` + spi_transfer_delay_exec()")
>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
/Jarkko
next prev parent reply other threads:[~2019-12-17 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:00 [PATCH] tpm_tis_spi: use new `delay` structure for SPI transfer delays Alexandru Ardelean
2019-12-09 19:50 ` Jarkko Sakkinen
2019-12-10 6:56 ` [PATCH V2] " Alexandru Ardelean
2019-12-11 17:37 ` Jarkko Sakkinen
2019-12-12 7:21 ` Ardelean, Alexandru
2019-12-17 1:26 ` Jarkko Sakkinen
2019-12-17 9:16 ` [PATCH V3] tpm_tis_spi: use new 'delay' " Alexandru Ardelean
2019-12-17 12:04 ` Jarkko Sakkinen [this message]
2020-02-26 7:51 ` Ardelean, Alexandru
2020-02-26 15:10 ` Jarkko Sakkinen
2020-02-26 15:11 ` Ardelean, Alexandru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9991700815c02b3227a5902e4cae1afe5200b0ff.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=alexandru.ardelean@analog.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).