From: patchwork-bot+netdevbpf@kernel.org
To: Stefan Wahren <wahrenst@gmx.net>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 0/3] qca_spi: collection of major fixes
Date: Sat, 09 Dec 2023 00:20:29 +0000 [thread overview]
Message-ID: <170208122916.21357.8920685426589017304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206141222.52029-1-wahrenst@gmx.net>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Dec 2023 15:12:19 +0100 you wrote:
> This series contains a collection of major fixes for the qca_spi driver,
> which has been recently discovered.
>
> Changes in V3:
> - Avoid race condition in qcaspi_set_ringparam() as reported by Jakub and
> move all traffic handling within qcaspi_spi_thread
> - use netif_tx_disable instead of netif_stop_queue
>
> [...]
Here is the summary with links:
- [V3,1/3] qca_debug: Prevent crash on TX ring changes
https://git.kernel.org/netdev/net/c/f4e6064c97c0
- [V3,2/3] qca_debug: Fix ethtool -G iface tx behavior
https://git.kernel.org/netdev/net/c/96a7e861d9e0
- [V3,3/3] qca_spi: Fix reset behavior
https://git.kernel.org/netdev/net/c/1057812d146d
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:[~2023-12-09 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 14:12 [PATCH V3 0/3] qca_spi: collection of major fixes Stefan Wahren
2023-12-06 14:12 ` [PATCH V3 1/3] qca_debug: Prevent crash on TX ring changes Stefan Wahren
2023-12-06 14:12 ` [PATCH V3 2/3] qca_debug: Fix ethtool -G iface tx behavior Stefan Wahren
2023-12-06 14:12 ` [PATCH V3 3/3] qca_spi: Fix reset behavior Stefan Wahren
2023-12-09 0:20 ` 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=170208122916.21357.8920685426589017304.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wahrenst@gmx.net \
/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