From: Kalle Valo <kvalo@codeaurora.org>
To: Sergiu Cuciurean <sergiu.cuciurean@analog.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-wireless@vger.kernel.org>,
<libertas-dev@lists.infradead.org>, <davem@davemloft.net>,
<gregkh@linuxfoundation.org>, <dcbw@redhat.com>,
<allison@lohutok.net>, <tglx@linutronix.de>,
Sergiu Cuciurean <sergiu.cuciurean@analog.com>
Subject: Re: [PATCH] libertas: Use new structure for SPI transfer delays
Date: Thu, 12 Mar 2020 13:43:02 +0000 (UTC) [thread overview]
Message-ID: <20200312134302.82B12C4478C@smtp.codeaurora.org> (raw)
In-Reply-To: <20200227140634.9286-1-sergiu.cuciurean@analog.com>
Sergiu Cuciurean <sergiu.cuciurean@analog.com> 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 bebcfd272df6 ("spi: introduce `delay` field for
> `spi_transfer` + spi_transfer_delay_exec()")
>
> Signed-off-by: Sergiu Cuciurean <sergiu.cuciurean@analog.com>
Patch applied to wireless-drivers-next.git, thanks.
32521a913852 libertas: Use new structure for SPI transfer delays
--
https://patchwork.kernel.org/patch/11408719/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-03-12 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 14:06 [PATCH] net: wireless: marvell: libertas: Use new structure for SPI transfer delays Sergiu Cuciurean
2020-03-12 13:43 ` Kalle Valo [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=20200312134302.82B12C4478C@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=allison@lohutok.net \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergiu.cuciurean@analog.com \
--cc=tglx@linutronix.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).