From: patchwork-bot+netdevbpf@kernel•org
To: Yue Haibing <yuehaibing@huawei•com>
Cc: kgraul@linux•ibm.com, wenjia@linux•ibm.com, jaka@linux•ibm.com,
alibuda@linux•alibaba.com, tonylu@linux•alibaba.com,
guwen@linux•alibaba.com, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
linux-s390@vger•kernel.org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH net-next] net/smc: Remove unused function declarations
Date: Mon, 31 Jul 2023 21:50:22 +0000 [thread overview]
Message-ID: <169084022252.13504.15977220371779488988.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230729121929.17180-1-yuehaibing@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Sat, 29 Jul 2023 20:19:29 +0800 you wrote:
> commit f9aab6f2ce57 ("net/smc: immediate freeing in smc_lgr_cleanup_early()")
> left behind smc_lgr_schedule_free_work_fast() declaration.
> And since commit 349d43127dac ("net/smc: fix kernel panic caused by race of smc_sock")
> smc_ib_modify_qp_reset() is not used anymore.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei•com>
>
> [...]
Here is the summary with links:
- [net-next] net/smc: Remove unused function declarations
https://git.kernel.org/netdev/net-next/c/4cbc32a8a2b4
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-07-31 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 12:19 [PATCH net-next] net/smc: Remove unused function declarations Yue Haibing
2023-07-30 17:25 ` Simon Horman
2023-07-31 2:11 ` Tony Lu
2023-07-31 7:26 ` Wenjia Zhang
2023-07-31 21:50 ` 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=169084022252.13504.15977220371779488988.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alibuda@linux$(echo .)alibaba.com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=guwen@linux$(echo .)alibaba.com \
--cc=jaka@linux$(echo .)ibm.com \
--cc=kgraul@linux$(echo .)ibm.com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=tonylu@linux$(echo .)alibaba.com \
--cc=wenjia@linux$(echo .)ibm.com \
--cc=yuehaibing@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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