From: patchwork-bot+netdevbpf@kernel.org
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3 net-next] net: qca_spi: Improve sync handling
Date: Mon, 10 May 2021 21:40:10 +0000 [thread overview]
Message-ID: <162068281060.31911.13009428589213016326.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1620477395-12740-1-git-send-email-stefan.wahren@i2se.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sat, 8 May 2021 14:36:32 +0200 you wrote:
> This small patch series contains some improvements of the sync
> handling. This was discovered while the QCA7000 was doing SLAC
> (Signal Level Attenuation Characterization).
>
> Stefan Wahren (3):
> net: qca_spi: Avoid reading signature three times in a row
> net: qca_spi: Avoid re-sync for single signature error
> net: qca_spi: Introduce stat about bad signature
>
> [...]
Here is the summary with links:
- [1/3,net-next] net: qca_spi: Avoid reading signature three times in a row
https://git.kernel.org/netdev/net-next/c/b76078df1593
- [2/3,net-next] net: qca_spi: Avoid re-sync for single signature error
https://git.kernel.org/netdev/net-next/c/6e03f3ff29c1
- [3/3,net-next] net: qca_spi: Introduce stat about bad signature
https://git.kernel.org/netdev/net-next/c/a53935674563
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-10 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 12:36 Stefan Wahren
2021-05-08 12:36 ` [PATCH 1/3 net-next] net: qca_spi: Avoid reading signature three times in a row Stefan Wahren
2021-05-08 12:36 ` [PATCH 2/3 net-next] net: qca_spi: Avoid re-sync for single signature error Stefan Wahren
2021-05-08 12:36 ` [PATCH 3/3 net-next] net: qca_spi: Introduce stat about bad signature Stefan Wahren
2021-05-10 21:40 ` patchwork-bot+netdevbpf [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=162068281060.31911.13009428589213016326.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
/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
all inboxes | Powered by JetHome®