From: patchwork-bot+netdevbpf@kernel.org
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
themsley@voiceflex.com
Subject: Re: [PATCH net 0/3] sfc: fix TXQ lookups
Date: Wed, 21 Apr 2021 00:10:09 +0000 [thread overview]
Message-ID: <161896380991.7038.8348862793426542295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <6b97b589-91fe-d71e-a7d0-5662a4f7a91c@gmail.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 20 Apr 2021 13:24:54 +0100 you wrote:
> The TXQ handling changes in 12804793b17c ("sfc: decouple TXQ type from label")
> which were made as part of the support for encap offloads on EF10 caused some
> breakage on Siena (5000- and 6000-series) NICs, which caused null-dereference
> kernel panics.
> This series fixes those issues, and also a similarly incorrect code-path on
> EF10 which worked by chance.
>
> [...]
Here is the summary with links:
- [net,1/3] sfc: farch: fix TX queue lookup in TX flush done handling
https://git.kernel.org/netdev/net/c/5b1faa92289b
- [net,2/3] sfc: farch: fix TX queue lookup in TX event handling
https://git.kernel.org/netdev/net/c/83b09a180741
- [net,3/3] sfc: ef10: fix TX queue lookup in TX event handling
https://git.kernel.org/netdev/net/c/172e269edfce
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-04-21 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 12:24 [PATCH net 0/3] sfc: fix TXQ lookups Edward Cree
2021-04-20 12:27 ` [PATCH net 1/3] sfc: farch: fix TX queue lookup in TX flush done handling Edward Cree
2021-04-20 12:28 ` [PATCH net 2/3] sfc: farch: fix TX queue lookup in TX event handling Edward Cree
2021-04-20 12:29 ` [PATCH net 3/3] sfc: ef10: " Edward Cree
2021-04-21 0:10 ` 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=161896380991.7038.8348862793426542295.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=themsley@voiceflex.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;
as well as URLs for NNTP newsgroup(s).