From: patchwork-bot+netdevbpf@kernel.org
To: Julian Wiedmann <jwi@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
kgraul@linux.ibm.com, wintera@linux.ibm.com
Subject: Re: [PATCH net 0/3] s390/qeth: fixes 2021-09-21
Date: Wed, 22 Sep 2021 03:10:07 +0000 [thread overview]
Message-ID: <163228020700.28047.10149739218296607530.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210921145217.1584654-1-jwi@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 21 Sep 2021 16:52:14 +0200 you wrote:
> Hi Dave & Jakub,
>
> please apply the following patch series for qeth to netdev's net tree.
>
> This brings two fixes for deadlocks when a device is removed while it
> has certain types of async work pending. And one additional fix for a
> missing NULL check in an error case.
>
> [...]
Here is the summary with links:
- [net,1/3] s390/qeth: fix NULL deref in qeth_clear_working_pool_list()
https://git.kernel.org/netdev/net/c/248f064af222
- [net,2/3] s390/qeth: Fix deadlock in remove_discipline
https://git.kernel.org/netdev/net/c/ee909d0b1dac
- [net,3/3] s390/qeth: fix deadlock during failing recovery
https://git.kernel.org/netdev/net/c/d2b59bd4b06d
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-09-22 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 14:52 [PATCH net 0/3] s390/qeth: fixes 2021-09-21 Julian Wiedmann
2021-09-21 14:52 ` [PATCH net 1/3] s390/qeth: fix NULL deref in qeth_clear_working_pool_list() Julian Wiedmann
2021-09-21 14:52 ` [PATCH net 2/3] s390/qeth: Fix deadlock in remove_discipline Julian Wiedmann
2021-09-21 14:52 ` [PATCH net 3/3] s390/qeth: fix deadlock during failing recovery Julian Wiedmann
2021-09-22 3: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=163228020700.28047.10149739218296607530.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wintera@linux.ibm.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