From: <Tudor.Ambarus@microchip.com>
To: <Thomas.Kopp@microchip.com>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH] spi: atmel: Exposing effective spi speed
Date: Mon, 21 Sep 2020 06:03:56 +0000 [thread overview]
Message-ID: <a0e687e1-0da1-d049-9c22-75c46fe197a3@microchip.com> (raw)
In-Reply-To: <fe705481-ef9e-4dfb-fa86-b138a8cbf4c9@microchip.com>
On 9/21/20 9:02 AM, Tudor Ambarus - M18064 wrote:
> Hi, Thomas,
>
> On 9/18/20 1:37 PM, Thomas Kopp wrote:
>> This patch implements the reporting of the effectively used speed_hz for the
>> transfer by setting xfer->effective_speed_hz.
>>
>> See the following patch, which adds this feature to the SPI core for more
>> information:
>>
>> 5d7e2b5ed585 spi: core: allow reporting the effectivly used speed_hz for a transfer
>
> s/effectivly/effectively
oops, please ignore this, don't change the commit subject.
prev parent reply other threads:[~2020-09-21 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 10:37 [PATCH] spi: atmel: Exposing effective spi speed Thomas Kopp
2020-09-21 6:02 ` Tudor.Ambarus
2020-09-21 6:03 ` Tudor.Ambarus [this message]
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=a0e687e1-0da1-d049-9c22-75c46fe197a3@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Thomas.Kopp@microchip.com \
--cc=linux-spi@vger.kernel.org \
/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).