From: patchwork-bot+netdevbpf@kernel.org
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
guvenc@linux.ibm.com, jwi@linux.ibm.com
Subject: Re: [PATCH net 0/2] net/smc: fixes 2021-09-20
Date: Tue, 21 Sep 2021 10:10:07 +0000 [thread overview]
Message-ID: <163221900762.14288.11996039064069209042.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210920191815.2919121-1-kgraul@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Mon, 20 Sep 2021 21:18:13 +0200 you wrote:
> Please apply the following patches for smc to netdev's net tree.
>
> The first patch adds a missing error check, and the second patch
> fixes a possible leak of a lock in a worker.
>
> Karsten Graul (2):
> net/smc: add missing error check in smc_clc_prfx_set()
> net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work
>
> [...]
Here is the summary with links:
- [net,1/2] net/smc: add missing error check in smc_clc_prfx_set()
https://git.kernel.org/netdev/net/c/6c9073198065
- [net,2/2] net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work
https://git.kernel.org/netdev/net/c/a18cee4791b1
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-21 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 19:18 [PATCH net 0/2] net/smc: fixes 2021-09-20 Karsten Graul
2021-09-20 19:18 ` [PATCH net 1/2] net/smc: add missing error check in smc_clc_prfx_set() Karsten Graul
2021-09-20 19:18 ` [PATCH net 2/2] net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work Karsten Graul
2021-09-21 10: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=163221900762.14288.11996039064069209042.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=guvenc@linux.ibm.com \
--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 \
/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